andy-chiles
Hi!
I tried to trigger a series of custom_buttons from inside another custom_button, but as soon as I write "custom_button XX" into my command inside some other "custom_button XYZ" and re-open the window of the exact button again, it became "nothing XX", so I'm not able to trigger the custom_button I wanted to trigger.
Why is that?
And is there a possibility to fix this?
- Thanks!
I tried to trigger a series of custom_buttons from inside another custom_button, but as soon as I write "custom_button XX" into my command inside some other "custom_button XYZ" and re-open the window of the exact button again, it became "nothing XX", so I'm not able to trigger the custom_button I wanted to trigger.
Why is that?
And is there a possibility to fix this?
- Thanks!
Posté 22 hours ago
locoDog
From the origin and by design a custom_button can't call a custom_button.
Reason is people would try to make infinite loops and that causes forced crashes.
As much as I'd like a realish forLoop ( ; ; ) for stuff scrolling the browser, I understand why there isn't one.
You can do stuff with pads calling pads, maybe even custom_buttons that write apoi that call custom_buttons, but you have to give it a 50ms rest every 1000 cycles or so to avoid the crashes, and at that point you're bending the script engine so far that if it breaks there can be no complaining.
Reason is people would try to make infinite loops and that causes forced crashes.
As much as I'd like a realish forLoop ( ; ; ) for stuff scrolling the browser, I understand why there isn't one.
You can do stuff with pads calling pads, maybe even custom_buttons that write apoi that call custom_buttons, but you have to give it a 50ms rest every 1000 cycles or so to avoid the crashes, and at that point you're bending the script engine so far that if it breaks there can be no complaining.
Posté 8 hours ago