Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!watson.ibm.COM!dan
From: dan@watson.ibm.COM (Walt Daniels)
Newsgroups: comp.windows.x
Subject: Double clicks
Message-ID: <101789.092040.dan@watson.ibm.com>
Date: 17 Oct 89 13:20:40 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 15

I think I prefer spacially resolved double clicks rather than time
resolved double clicks.  These can be handled entirely on the client
side with only the two button events coming from the server.  Thus the
client should (if is implements double clicks at all) enter a state
machine after a click and not do anything until either another click
near the first click spacially, sufficient mouse motion to be outside
the space of the first click, a keystroke, or some longish time.

In general I think double clicks are a poor human interface and
are really a poor substitute for a mouse with sufficient buttons.  The
reason it is a poor interface is that the program can never be
responsive to the user until the second event whether time or space
resolved.  In other words one click can never have a useful meaning
other than enter complicated state machine.
Walt Daniels