Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!bellcore!spectral!sjs
From: sjs@spectral.ctt.bellcore.com (Stan Switzer)
Newsgroups: comp.windows.news
Subject: Re: Help with double-click recognition.
Message-ID: <18015@bellcore.bellcore.com>
Date: 23 Oct 89 14:37:53 GMT
References: <603@granite.dec.com> <1922@bacchus.dec.com> <1490@esquire.UUCP> <6564@ficc.uu.net> <17943@bellcore.bellcore.com> <6594@ficc.uu.net>
Sender: news@bellcore.bellcore.com
Reply-To: sjs@bellcore.com (Stan Switzer)
Organization: Bellcore
Lines: 17

In article <6594@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:

> Click-hold is a different matter... you don't need to use the time domain:
> just see if the current position changes while the button is down. Doesn't
> everyone do it this way?

Yes, we do.  But what if the mousie doesn't move?

No matter:  In NeWS, it's easy to do this kind of event processing.
Just wait for whichever happens first: timeout, click, or for the
mouse movement more than a jiggle.  AND, if you are careful about how
you use blockinputqueue/unblockinputqueue, you'll never miss an event.
(I guess that this is the problem with double-click in X, but as I
said before, it strikes me as quite odd that you can't detect
multi-clicks in X.)

Stan  sjs@bellcore.com