Re: Input issues - key down with no key up

From: Jamie Lokier <jamie@shareable.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Vojtech Pavlik <vojtech@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: Input issues - key down with no key up
Date: Thu, 21 Aug 2003 01:03:02 +0100	[thread overview]
Message-ID: <20030821000302.GC24970@mail.jlokier.co.uk> (raw)
In-Reply-To: <20030821015258.A3180@pclin040.win.tue.nl>

Andries Brouwer wrote:
> > Synthesising an UP event after receiving a DOWN from the keyboard, and
> > nothing else for that key for > (repeat delay + a bit more) time looks
> > like a good plan to me, UNLESS there are keys which do report UP when
> > the key is released (as opposed to immediately after the DOWN), and
> > also don't repeat.
> 
> And there are keyboards with such keys.

Alas.

For programs which are only interested in key presses, there is no
problem including a synthesised UP event.

But for programs which want to monitor a key and know its state
continuously (this presently includes the software autorepeater, but
it also includes games), none of the behaviours is right.

So the decision must be: shall we do the wrong thing for keyboards
which report DOWN only (the key will appear stuck to some programs),
or shall we do the wrong thing for keyboards which report DOWN, no
repeat and then UP, by making it look like the key was released early?

-- Jamie