Quote from
raphael on 8 December 2025, 18:06
:wave:
I noticed that macro execution takes a bit - I suspect this is due to the subprocess creation and python parsing/ processing time for my macros.
EG, even simple macros that just call print() for debugging add a noticeable execution lag. This is not great when plasma cutting because the torch dwells for a bit.
Any chance we can get SimCNC macros to work without the current CGI-like process creation?
Is there any solution to this that people commonly use? If not, @CSLab support what are the chances of you adding a feature for HTTP-2 push integration, or a "proper" SDK where I can just write Java for my macros?
:wave:
I noticed that macro execution takes a bit - I suspect this is due to the subprocess creation and python parsing/ processing time for my macros.
EG, even simple macros that just call print() for debugging add a noticeable execution lag. This is not great when plasma cutting because the torch dwells for a bit.
Any chance we can get SimCNC macros to work without the current CGI-like process creation?
Is there any solution to this that people commonly use? If not, @CSLab support what are the chances of you adding a feature for HTTP-2 push integration, or a "proper" SDK where I can just write Java for my macros?