Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!bloom-beacon!SHAMASH.MCRCIM.MCGILL.EDU!mouse
From: mouse@SHAMASH.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re:  Accelerator improvments wanted
Message-ID: <9006040207.AA08413@shamash.McRCIM.McGill.EDU>
Date: 4 Jun 90 02:07:57 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 44

> [is having problems with Xt accelerators]
> The difficulty is that there is no facility designed into the event
> translation mechanism for distinguishing temporal space between
> keystrokes, i.e.  "ST" is indistinguishable from "S"-wait-days-"T".

Or elsewhere, such as with pointer motion or button events.

> So problems remain.  Here are possible changes to X or the toolkit
> that would solve them.

> 1) Enhance the X server (and protocol) to define an optional
>    "timeout" event after each keystroke and button press.

I'd like to see it available after button releases and pointer motions
as well.  To handle double clicks properly, it must be available after
button releases, in fact; otherwise  push-release-wait-push-release
(two single clicks) will be indistinguishable from
push-release-push-release (a double click), since neither one will
generate any timeout events.

>    An X call would set the timeout interval for a given window.

Are you sure the window is the right thing to use as the handle for
setting the timeout?  I think it should be the (window,client) pair,
the way event masks already are.

Ideally, it should be possible to set different timeout times for each
event which is set to generate a timeout, but that's probably more than
is necessary.

>    The advantage of this is that the time-critical measurements are
>    made on the server side, where the user is, not on the client
>    side, potentially halfway around the world.

Precisely.

I've been annoyed for some time because it is not currently possible to
handle multiple mouse clicks correctly.  I'm glad someone else sees the
need for timeout events....

					der Mouse

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