Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!think!mintaka!mit-eddie!uw-beaver!uw-june!dylan
From: dylan@cs.washington.edu (Dylan McNamee)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Double Click
Message-ID: <11002@june.cs.washington.edu>
Date: 7 Mar 90 21:07:46 GMT
References: <79yO02zd8fMp01@amdahl.uts.amdahl.com>
Reply-To: dylan@june.cs.washington.edu (Dylan McNamee)
Organization: University of Washington, Computer Science, Seattle
Lines: 27

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.

It's really important to respect preferences settings.  New users
usually like the double-click time to be fairly large, and it
tends to shrink with mouse-experience...

>
> this is Genocide!"       |Dave Lowrey - Amdahl Corp. - Houston, TX

dylan mcnamee
dylan@cs.washington.edu