Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!ingr!doyle
From: doyle@ingr.com (Doyle Davidson)
Newsgroups: comp.windows.x
Subject: Re: Single/Double Click
Message-ID: <9676@ingr.com>
Date: 9 Apr 90 22:00:11 GMT
References: <9004080623.AA02917@Larry.McRCIM.McGill.EDU>
Organization: Intergraph Corp. Huntsville, Al
Lines: 42

In article <9004080623.AA02917@Larry.McRCIM.McGill.EDU>, mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse) writes:
> 
> I think X should have mouse timeout events of some sort, that is, some
> sort of event that can be requested saying that "the mouse hasn't
> changed state in <time>",
 
> Perhaps if nobody else does I'll put together an extension and see how
> it goes.
> 
> 					der Mouse
Don't bother, I have already done it.  It is a little complicated because
you have to handle pointer grabs correctly but it is doable.
Probably about 100 lines of hacking in "event.c" plus the 
extension registration stuff, Xlib bindings, and the signalling 
mechanism in the server.  It makes multiple clicks
easy to recognize without a timer.  But I don't know if it can
be wedged into Xt easily.  We use it proprietarily. (Is that a word?
English always was my worstest subject)

There are other issues like what happens when you:
    in window 1: <Down> <Up> 
	then move to window 2 quickly and click again
Each window gets it's own up/down combo but where do
you send the timeout to?  Both? just the last?
What I did was force a pseudo timeout on the leave.

I would prefer to find a way to do it as an X input extension in R4
so that "events.c" is left untouched from MIT, but it is so intimately
tied to the mouse.  

Doyle
-------------------------------
Doyle C. Davidson              
Intergraph Corp.               
Workstation Graphics Standards 
1 Madison Industrial Park      
Huntsville, AL 35806           
(205) 730-2000                 
                               
..!uunet!ingr!b11!doyled!doyle 
    or   doyle@ingr.com
-------------------------------