[BUG][OSX][FIX?] Event delays
Tim Rowledge
tim at sumeru.stanford.edu
Tue Feb 13 00:37:13 UTC 2001
Henrik Gedenryd <Henrik.Gedenryd at lucs.lu.se> is widely believed to have written:
> Marcel Weiher wrote:
>
> > I suggest that the fix to double-click detection that was proposed
> > on this list earlier should be implemented (and will try it myself
> > now in order to see what happens): send a #click: after the first
> > mouseUp event, and make sure that the few existing #doubleClick:
> > clients can deal with receiving a click before the double-click.
>
> This is actually how a double click should always be designed. It should
> always be signalled as a click event followed by a double click event, and
> all uses of double click should be natural extensions of a single click.
> E.g. single click selects object, double click performs most frequent action
> on it.
Exactly! There might even be a neat way to use the double-click events
that many OS's provide, usurping the image's spending time on working it
out.
tim
--
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
To steal ideas from one person is plagiarism; to steal from many is research.
More information about the Squeak-dev
mailing list
|