Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!think.com!mintaka!bloom-beacon!dont-send-mail-to-path-lines
From: mouse@lightning.mcrcim.mcgill.EDU
Newsgroups: comp.windows.x
Subject: Re:  Wanted: info on DOUBLE CLICKING displayed images
Message-ID: <9101301102.AA20743@lightning.McRCIM.McGill.EDU>
Date: 30 Jan 91 11:02:19 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 24

> In this world of mice and windows, it seems that everyone (OpenLook,
> Motif, Microsoft, etc) lets you DOUBLE CLICK displayed images in
> order to initiate an action (load, open, etc.).

> It would seem that the way to do this is to set timers and flags and
> trap the DC event in your own code.

At present, this is how you have to do it.  The current protocol does
not support anything that will let you do this correctly.

> Thats what I'm doing, and it works fine...

It works fine in your tests, because the machines involved are not
overloaded and the network between them is fast and working.  In the
presence of overloaded machines and/or flaky networks, it is possible
for the user to double-click, but for the first click to reach the
client fast and the second click to be delayed, so as to make them
appear to be two single clicks.  (IMO this situation needs
improvement.)

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu