Path: utzoo!attcan!uunet!aplcen!samsung!xylogics!merk!spdcc!tauxersvilli!alphalpha!nazgul
From: nazgul@alphalpha.com (Kee Hinckley)
Newsgroups: comp.windows.x
Subject: Re:  Single click vs double click
Message-ID: <1990Oct25.134922.2900@alphalpha.com>
Date: 25 Oct 90 13:49:22 GMT
References: <9010180741.AA14602@Larry.McRCIM.McGill.EDU> <123770@linus.mitre.org> <1990Oct24.194348@Pkg.Mcc.COM>
Organization: asi
Lines: 27

In article <1990Oct24.194348@Pkg.Mcc.COM> harp@Pkg.Mcc.COM (Christopher North-Keys) writes:
>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.
...
>Incoming button event:
>	If the icon is unselected:  select
>	If the icon is selected:    edit

Note that that doesn't solve the problem either.  The highlight
of a selected item involves a trip to the server.  Given a server
load or network problem (the same things which screw up double
click) the highlight may not appear immediately and so the user
may click again thinking they didn't get it the first time.
Now instead of having them sometimes not get the double click
action, they'll sometimes get the double click action when they
wanted single - which is probably worse.  Given a multi-tasking
machine I don't think you can ever get this right, but building
double click support into the server would help.
-- 
Alphalpha Software, Inc.	|	motif-request@alphalpha.com
nazgul@alphalpha.com		|-----------------------------------
617/646-7703 (voice/fax)	|	Proline BBS: 617/641-3722

I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.