mouseup/mouseDoubleU
Jim Lambert
jiml at netrin.com
Tue Feb 1 14:47:15 EST 2011
On Feb 1, 2011, at 10:00 AM, Craig wrote:
> If you have this in a button script:
>
> on mouseUp
> put "single"
> wait 15
> put "" --just to see it work
> end mouseup
>
> on mouseDoubleUp
> put "double"
> wait 15
> put "" --just to see it work
> end mouseDoubleUp
>
> you can get all sorts of behaviors if you click at various rates. Sometimes
> you even get what you want, that is, a single response to a double click.
> This takes practice and luck, though, and that seems contrary to clean,
> robust programming methodology.
>
> Jim, can you elaborate on your idea of passing mouseup? How and where would
> you do that?
>
>
I was guessing that trapping a single mouseUp might affect the doubleUp. But it doesn't. So ignore that suggestion!
When I try this without any 'waits':
on mouseUp
put cr & "single" after msg
end mouseup
on mouseDoubleUp
put cr & "double" after msg
end mouseDoubleUp
I get the expected output. The mouseUp is always triggered. The mouseDoubleUp only triggers if I meet the doubleclickinterval and doubleclickdelta as Peter noted.
Jim Lambert
More information about the use-livecode
mailing list