Re: How to avoid errant mouse events?

[David Vaughan]

On Tuesday, December 10, 2002, at 09:04 AM, Monte Goulding wrote:

Well if you want to avoid a double-click then you can just put
on mouseDoubleUp
end mouseDoubleUp

I think it was Sarah who previously suggested a refinement where you put in the card or stack script:

on mouseDoubleUp
send mouseUp to the target
end mouseDoubleUp

which ensures all the clicks are captured, if that is what you want.

regards
David

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

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution