Not speaking as an authority, just from my own experience "exit xyz" exits the current handler, and allows a calling handler to continue executing, if present
"exit to top" exits and stops executing the current handler and any calling handler if present; any pending messages will be sent "send xyz to me in 200 millisecs" allows other messages/events to take place "wait until <condition> with messages" allows other messages/events to take place (in what I think of as being an ultra-tight repeat loop) If you want to cancel a message that has been sent in time, you can: 1) grab the id upon sending the message to be canceled later 2) do a "repeat for each" in the pending messages to find the line containing the message name and cancel it 3) cancel all the pendingMessages Hope this helps. Regards, Scott Rossi Creative Director Tactile Media, UX Design On 10/2/12 6:15 PM, "dunb...@aol.com" <dunb...@aol.com> wrote: >But as Bernd notes, why the "exit to top" doesn't kill everything is >still a mystery... _______________________________________________ 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
