How to "communicate" between macro & plugin/macroloop

[dezsoe]

Hi Keith,

Yes, it's a good idea. If you have to run a long process then start a new thread and do it there.

It's not easy to find out what Terry wanted to suggest. Macroloops and plugins run if you set them to run: no problem. Macros, of course, cannot always run. You cannot start a macro in reset or while g-code is running. (You can call a macro from the running g-code, but cannot start one with a button.) I think, there's no magic knowledge, you just have to think: is it normal to run a macro this or that way?

[Vmax549]

In UCCNC there are instances where UCCNC will fail to run functions due to safety concerns. I wrote on this long ago. Balaiz said it was written to be that way. And that is his decision to make it that way. But sometimes it just delays a function and then runs it at the end of a gcode file. Not a good idea.

IF UCCNC is not going to run a function due to safety concerns it SHOULD post a error message to the user to alert them that there IS a problem and they have the choice to continue or abort.

It mainly shows up in macroloops that trigger other functions such as triggering plugins and functions when Gcode is running.

Just a thought, (;-) TP