Re: Input issues - key down with no key up

[Jamie Lokier <jamie@shareable.org>]

Vojtech Pavlik wrote:
> > That works well for typing, but if someone tries to use these keys in
> > an action game, they will disappointed with the forced-up code - the
> > game will see the key pressed and released, even when the user holds
> > the key down for a long time.
> 
> Indeed. Are you expecting a game to be able to use the WWW or Calculator
> keys for anything useful?

Of course.  It's not unusual for a game to have a "define keys"
option, where you press a key for each action, to set the key
bindings.  Sometimes you pick mnemonic keys; other times, you pick
keys because of how their position feels, like making a custom joypad.

On my Microsoft multimedia keyboard there are about 20 keys that I
could see being useful for that, especially as mnemonic keys.

> > There is only one solution which works well that I can see: do the
> > forced-up thing by default, but as soon as you see a real UP event
> > from a key, disabled forced-up _for that key_ in future.
> 
> Won't work. There are keyboards that forget to send a key up event
> sometimes. They usually send it, but from time to time they don't.
> We need to cover these keyboards, too. It's actually the main reason for
> the whole forced up thingy.

:(  That's a shame, and a peculiar bug too.  Then I agree that
forced-up is needed all the time, if we do not know what triggers the
keyboard to forget to send one or have any way to detect it.

It is not so bad, because even the multimedia keys will be fine on
good quality keyboards.

> I'll give you a kernel/module option to disable the forced up effect if
> you have a perfect keyboard. You can then also enable the untranslated
> mode and set 3. But the default will be translated set 2 with forced
> keyups if a key is not repeating.

Fair enough, I agree.

-- Jamie