Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: Help with double-click recognition.
Message-ID: <3954@helios.ee.lbl.gov>
Date: 14 Oct 89 00:26:14 GMT
References: <1922@bacchus.dec.com> <603@granite.dec.com>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: Lawrence Berkeley Laboratory
Lines: 34

In article <1922@bacchus.dec.com>, asente@decwrl.dec.com (Paul Asente) writes:

(But first, someone else:)
< >I've
< >tried in many ways to figure out how to get it to call one
< >callback on a single button press, and another for a double-click.  
< >So far, I've not been succesful, and it seems from my understanding
< >of the documentation and from my experimentation that it might not
< >be possible.
<
< You got it.
< 
< There really is a reason for it.  X is network-based.  There's no way for
< an application to know, upon receiving one button click, whether there's
< another one coming along.  Consider the following scenario:
<

[...]
 
<  It has nothing to do with the
< toolkit; it's intrinsic to X.
< 


Wait a second!
What about xterm's double/triple click and xrn's double/triple/quadruple
click recognition for text selection?

Please explain how that works so well 8-)

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.