Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!biar!trebor
From: trebor@biar.UUCP (Robert J Woodhead)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Double Clicking
Message-ID: <150@biar.UUCP>
Date: 25 Feb 89 03:53:05 GMT
References: <4452@hubcap.UUCP> <1967@helios.ee.lbl.gov> <Feb.24.08.37.59.1989.6111@athos.rutgers.edu>
Reply-To: trebor@biar.UUCP (Robert J Woodhead)
Organization: Biar Games, Inc.
Lines: 25

In article <Feb.24.08.37.59.1989.6111@athos.rutgers.edu> wiechman@athos.rutgers.edu (NightMeower) writes:
>Also, you'll want to compare the mouse locations to see if they are
>sufficiently close together.  Consider a user doing fast but detailed
>work.  Two clicks very close together in time, but far apart in
>location could be misinterpretted as a double click.

Very true.  In general, the double click "heuristic" is:

if (curTime-lastClickTime)<maxDoubleClickTime then
  if object_clicked_on = last_object_clicked_on then
     double_click(object_clicked_on);

As mentioned, it's VERY important that you ensure that the two clicks are
not only temporally close but SEMANTICALLY close; an example of an app that
does not do this in the current release is Compuserve Navigator when you are
selecting threads to retrieve -- if you click on an item and then click on
another item quickly, it thinks you double clicked on the second item; this
is disconcerting.

+---------------------------------------------------------------------------+
| Robert J Woodhead      !uunet!cornell!biar!trebor     CompuServe 72447,37 |
| Biar Games, Inc., 10 Spruce Lane, Ithaca NY 14850  607-257-1708,3864(fax) |
+---------------------------------------------------------------------------+
| Games written, Viruses killed   "I'm the head honcho of this here spread; |
| While U Wait.  Take a number.    I don't need no stinking disclaimers!!!" |
+---------------------------------------------------------------------------+