Command registration

[gswifort]

Can you expose this function in Ap module? This would be useful e.g. for marking functions as commands via a decorator instead of giving them a name with the prefix PyRxCmd_.

PyRx/PyRxCore/PyRxModuleLoader.cpp

Line 120 in 7cabe18

static void loadCommands(PyRxMethod& method, const PyModulePath& path)

import traceback

# instead of this:
def PyRxCmd_doit():
    try:
        print("Hello")
    except Exception:
        traceback.print_exc()

# it could be:
@command(name="doit")
def main():
    print("Hello")

[CEXT-Dan]

That’s probably the way it should have been. That’s kind of what GstarCAD does.
Also their command flags (testCmdFlags.py).

@command()  
def gdoit():
    try:
        ...
    except Exception as err:
        print(err)

@command(NOHISTORY | NOBEDIT)  
def gdoit():
    try:
        ...
    except Exception as err:
        print(err)

I had taken inspiration from lisp

     c:defun()

    static void AcRxPyApp_pyload(void)

I thought about changing it, I didn’t know how (I still don’t) to make the decorator, and how to find it with the relationship to the target function from the dictionary

Also, this had a slightly dangerous side effect if you change the decorator to point at a new function, then pyreload

Now, I feel it’s baked in. I have samples all over the internet now. this change will break everyone's code

[a-fakhri]

Now, I feel it’s baked in. I have samples all over the internet now. this change will break everyone's code

Could you implement the decorator while not depreciating the prefix option (i.e. PyRxCmd_)? You could depreciate the prefix option further down the line.

[CEXT-Dan]

Good thought, I don’t see a reason why they can’t coexist