I thought that, too. I don't know why my whole life I believed that the event queue was suspended during "wait".
It certainly makes sense, in hindsight, that a repeat loop would work that way. Sorry I mentioned it. After all, I have interrogated the mouse during loops as a matter of course. Who hasn't? Just got stuck in a loop, I guess. Craig Newman On Mar 22, 2009, at 2:03:16 PM, "J. Landman Gay" <[email protected]> wrote: Makes sense. The handler runs to completion before it processes any mouse clicks. So it waits (during which you click B), then goes to stack A (which it is already on) and then notices you clicked and goes to B. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
