Path: utzoo!attcan!uunet!cs.utexas.edu!milano!cadillac!Pkg.Mcc.COM!harp
From: harp@Pkg.Mcc.COM (Christopher North-Keys)
Newsgroups: comp.windows.x
Subject: Re:  Single click vs double click
Message-ID: <1990Oct24.194348@Pkg.Mcc.COM>
Date: 25 Oct 90 00:43:48 GMT
References: <9010180741.AA14602@Larry.McRCIM.McGill.EDU> <123770@linus.mitre.org>
Sender: news@cadillac.CAD.MCC.COM
Reply-To: harp@Pkg.Mcc.COM (Christopher North-Keys)
Lines: 26

Ideally, the idea of double-click event should be unnecessary.  What
should be done instead is to use a proper state model instead of trying
to use a time-dependent input type.

For example:

Let's consider the standard select(single-click)/edit(double-click) ---
if the programmer has sufficient control, the use of double-clicking
can be easily obviated, so:

Incoming button event:
	If the icon is unselected:  select
	If the icon is selected:    edit

I am, of course, biased --- I *despise* double clicking.  It tends to be
substantially more difficult to program, and forces user-specific 
parameters to define the single/double time threshold.  The only reason
it seems the double click was ever used was to compensate for crippled
mice with only *ONE* button.  Multibutton mice don't need this kind of cruft.


--
______________________________________________________________________________
Christopher Alex.North-Keys                          Associate Systems Analyst
Group Talisman                                                  Harp[@Mcc.Com]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~