Thanks Sarah and Scott,
I have tried in the past to trap the missed mousedown when they go
through, but its a real pain since there are a lot of possible
buttons it may have been intended for and i need to go through the
list of them to see if the clickloc was with each to find who should
get the mousedown message sent to it again.
If i cant figure out whats causing this i amy have to resort to this
work around. this one is puzzling. no clear pattern other than
timing. never seems to happen if a couple of seconds elapses between
clicks. this one is frustrating! i have tried moving the sequence of
what goes on to bring up the group with the buttons that then miss a
quick mousedown event, flushing events, etc to no avail.
cheers,
jeff
Jeffrey Reynolds
On May 31, 2007, at 10:13 PM, [EMAIL PROTECTED]
wrote:
The problem is once and a while a mouse down event is not caught by
revolution. it appears to usually happen after clicking on a button
that brings up a different group and then when you quickly try to
click on one of the newly visible group's buttons quickly the
mousedown is not captured on the object that is clicked on (like a
transparent button). the mousedown message does go onto the card
level though.
I don't know why the problem occurs, but if you get the mouseDown
message at the card level, what is "the target" at that stage? If "the
target" is actually the button you wanted to click, you could use that
to trigger the correct script.
Another possibility would be to set a flag when mouseDown was handled
and if a mouseUp or mouseStillDown message arrived without the
mouseDown having happened, you could send the mouseDown directly.
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
