It appears that on 9/6/99 8:52 AM, Gregory Lypny [EMAIL PROTECTED]
wrote:
>
> I've created a simple stack with navigation buttons that take the
>user to the next or previous card. My problem is that the buttons
>respond only to slow, deliberate clicks, and not to faster clicks (which
>are not double-clicks) that would allow the user to "flip" through the
>cards quickly. The buttons contain the common script (e.g.):
>
> on mouseUp
> go next cd of this stack
> end mouseUp
>
<snip>
>
> If the user clicks a navigation button two times in near succession,
>the second click appears to be ignored on my iMac. What am I doing wrong?
>
This is because the second click is being sent under the "mouseDoubleUp"
message. In order to fix this, I believe all you have to do is add this:
on mouseDoubleUp
send mouseUp to me
end mouseDoubleUp
Scott, Kevin--is there a better way to handle this? Would it be a
reasonable feature request to make the delivery of mouseDoubleUp
optional? On the Mac, it's a rare button that exhibits this behavior. The
only example I can think of is tools that lock into use when you double
click them. Is this behavior more common on Windows or Unix?
gc
Geoff Canyon [EMAIL PROTECTED]
"C.D. Caterpillar teaches kids how to read, not how to watch cartoons."
