Well if you want to avoid a double-click then you can just put on mouseDoubleUp end mouseDoubleUp
into your script. > > I posted this question under another subject name but will ask again as > I have not received any response yet. > > How do I prevent my app from registering that a second mouseUp event > has happened on an object while it is already performing the handler > that resulted from the first mouseUp? I've tried flushEvents(all) and > flushEvents(mouseUp) but it seems to crash Rev every time. Perhaps I'm > calling this at the wrong time? I'm now using lockMessages and it seems > to work but I'm wondering if I'm introducing something that will come > back to haunt me later on in the development process. > > Thanks, > Barry > > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
