On 10/2/12 7:49 PM, dunb...@aol.com wrote:
Does the existence of a pending message block a new call to that very handler from another source? The stop works if the code runs as shown. It fails if the repeat construct is commented out. That is what I am trying to understand.
The exit to top will abort the current handler and all of the handlers that called the current one (basically everything that's currently running.) Pending messages aren't running yet so there is nothing to abort there. As soon as the abort happens, the waiting pending message fires and the showRandoms handler starts up again.
-- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ 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
