Lock screen and animated gif
bobsneidar at iotecdigital.com
Tue Dec 20 17:18:05 EST 2022
<snip> this is the exact same thing I was experiencing a few years back which got me away from even referring to the defaultStack. Or topStack for that matter. I was using wait and send in time a lot back then. Now I explicitly refer to a stack by it's filename or better yet a card by it's long id.
On Dec 20, 2022, at 10:10 , Mark Waddingham via use-livecode <use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>> wrote:
On 2022-12-20 15:48, Paul Dupuis via use-livecode wrote:
I'm just using this post to raise awareness on the list (if anyone
reading this doesn't know this already)
When using 'wait 0 with messages' any messages in the pendingMessages
(who are not delayed in time) get processed. This includes
(potentially) user clicks (mouseDown and mosueUp events). In a
multi-window application, this can be a click on another window,
changing the defaultSTack. If the original script with the 'wait 0
with messages' does not use fully qualified object references, script
execution errors can result. Example:
My (admittedly quick!) tests indicate that this isn't entirely accurate...
Engine generated messages (e.g. mouseUp) behave differently in this regard to pending messages - and even in that case it requires specific action in script for it to occur.
So imagine you have a button on stack "S1" which has a single field on it. The button has script:
More information about the use-livecode