Posted: 11 Sep 2017, 02:30
In the scripting language, you have:
ProcessIDLE
This procedure is called at the setup refresh speed (around 25ms or 50ms). It's the place where you do calculation which doesn't need a fast speed, IML or graphic stuffs like SendInternalMsg (see bellow).
Why is there not a similar thing in the SDK ?
I have a large update process (recreating a tree for menu display) that is causing problems in onProcess(). How can I draw it in the non-audio thread in an SDK user module ?
I suppose I could do it before redrawing in onPaint() if a flag is set but that seems like a bad solution.
Also, in a SDK user module can the callbacks be set like they can in scripting, like this quote from the scripting reference:
The callback is provided at messages rate, typically every 25 or 50ms depending on the setup refresh speed.
To ensure a faster callback (immediately after the inlet has been modified) use the SetFastCallBack procedure describe bellow.
Thanks,
Simon.
ProcessIDLE
This procedure is called at the setup refresh speed (around 25ms or 50ms). It's the place where you do calculation which doesn't need a fast speed, IML or graphic stuffs like SendInternalMsg (see bellow).
Why is there not a similar thing in the SDK ?
I have a large update process (recreating a tree for menu display) that is causing problems in onProcess(). How can I draw it in the non-audio thread in an SDK user module ?
I suppose I could do it before redrawing in onPaint() if a flag is set but that seems like a bad solution.
Also, in a SDK user module can the callbacks be set like they can in scripting, like this quote from the scripting reference:
The callback is provided at messages rate, typically every 25 or 50ms depending on the setup refresh speed.
To ensure a faster callback (immediately after the inlet has been modified) use the SetFastCallBack procedure describe bellow.
Thanks,
Simon.