Re: Input issues - key down with no key up

[Vojtech Pavlik <vojtech@suse.cz>]

On Thu, Aug 21, 2003 at 01:03:02AM +0100, Jamie Lokier wrote:
> 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?

I vote for the synthetised event and possibly making it disableable.
It's a much bigger annoyance if your key stays stuck than if it goes up
even when you're holding it. And remember that the keys affected will
probably be special function keys only.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR