🚀 go-pugleaf

In article <11002@june.cs.washington.edu> dylan@june.cs.washington.edu (Dylan McNamee) writes:
>In article <79yO02zd8fMp01@amdahl.uts.amdahl.com> dwl10@uts.amdahl.com (Dave Lowrey) writes:
>>I can find no "standard" coding technique to handle "double clicking"
>>of a gadget.
>>
>>My guess would be:
>>   o When a gadget is selected, start a timer
>>   o If the timer elapses, then we won't have a double click.
>>   o If the user selects our gadget before the timer runs out, then
>>     consider that a double click.
>>
>>What is the "best" value to use when timing a double click?
>               ^
>NO Question Here!  Use the preferences value...I think you get
>it through some twisted set of getPrefsMumble calls.
>
>Once the prefs double click interval is read, your description
>_is_ practically an example of doing double-clicks.

	Oh, close, but not quite.

	There's an intuition.lirary call, DoubleClick().  You use it
thus:

	o You get a SELECTDOWN, the first click.  Pull the time out of
the IntuiMessage.
	o You get another SELECTDOWN, and decide it's the same gadget.
	o Pass both the first time value (the one you saved) and the
second to DoubleClick() and it will return TRUE if the two are closely
enough spaced to be considered a double-click.

	Please, don't do it the way GEM does it.  GEM must wait the
double-click interval before acting upon the first click, to be sure
it's not a double click.  In the Amiga, the first click is a selection,
the second is launch.  Act upon both.