It's my understanding that wait allows idle messages from the engine to be sent. When that happens, any send in time messages are processed. Wait with messages allows any other messages including engine messages to be processed.
For instance, I have a FindBar object that uses wait 1 second with messages in a keyDown handler so that as the user continues to type the keystrokes can be processed. If the user pauses for 1 or more seconds, the code that performs the find is triggered, and then I exit to top to prevent any more unnecessary processing (otherwise the loop would keep going until all the keystrokes were processed). Bob S > On Aug 1, 2022, at 12:43 , Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Now I am very curious about exactly what wait 0 with messages does and also > about what actions change the defaultStack. Does anyone know of an article or > something someone has done to identify all the messages, commands, or > functions that change (or potentially change) the defaultStack? _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
