oh that's understandable... I never use wait, because it messes up messages.
On 1 Feb 2011, at 17:42, dunb...@aol.com wrote: > This might need a new thread title. > > 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? > > Craig > > > > In a message dated 2/1/11 11:19:00 AM, j...@netrin.com writes: > > >> You might also try comparing the effect on your mouseDoubleUp of passing >> the mouseup vs. not passing the mouseup. >> >> > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
