It sounds like your "mouseUp" is considered a message, rather than an event- since you are generating it yourself rather than it coming from an event queue. We wouldn't want FlushEvents() to cancel all of the pending messages, no? I think it may just be a coincidence due to the fact you are sending your own mouseUps, perhaps it would be clearer to send yourself a custom message and use "cancel"?

- Brian

tried it. in the message, in the stack, in a palette just to be shure...

Tried what's written in the reference.

Is it a bug?

using a conditional whether to send the next mouseup cleaned the queue but
it's puzzling that it doesn't work...


I'll test RR...

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Scott Rossi
Sent: Friday, February 06, 2004 20:32
To: [EMAIL PROTECTED], Discussions on Metacard
Subject: Re: Flushing events


Recently, "MisterX" wrote:


Any experience anyone?

get flushevent("mouseup") doesn't remove my mouseup events... ;(((

Try flushEvents() [plural].


Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design
-----
E: [EMAIL PROTECTED]
W: http://www.tactilemedia.com

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

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



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

Reply via email to