How to avoid errant mouse events?
dvk at dvkconsult.com.au
Mon Dec 9 18:11:01 EST 2002
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:
send mouseUp to the target
which ensures all the clicks are captured, if that is what you want.
> into your script.
>> I posted this question under another subject name but will ask again
>> 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
>> to work but I'm wondering if I'm introducing something that will come
>> back to haunt me later on in the development process.
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the Use-livecode