Date: Mon, 25 Aug 2003 05:22:35 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andries Brouwer <aebr@win.tue.nl>, Neil Brown <neilb@cse.unsw.edu.au>,
       linux-kernel@vger.kernel.org
Subject: Re: Input issues - key down with no key up
Message-ID: <20030825042235.GB20529@mail.jlokier.co.uk>
References: <16188.54799.675256.608570@gargle.gargle.HOWL> <20030815135248.GA7315@win.tue.nl> <20030815141328.GA16176@ucw.cz> <16189.58357.516036.664166@gargle.gargle.HOWL> <20030821003606.A3165@pclin040.win.tue.nl> <20030820225812.GB24639@mail.jlokier.co.uk> <20030821015258.A3180@pclin040.win.tue.nl> <20030821080145.GA11263@ucw.cz> <20030822022709.A3640@pclin040.win.tue.nl> <20030822073328.GA7473@ucw.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030822073328.GA7473@ucw.cz>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2013
Lines: 48

> >   Serge van den Boom reports that his LiteOn MediaTouch Keyboard
> >   has 18 additional keys: Suspend, Coffee, WWW, Calculator, Xfer,
> >   Switch window, Close, |<<, >|, [], >>|, Record, Rewind, Menu,
> >   Eject, Mute, Volume +, and Volume -. Of these, the keys |<<,
> >   >>|, Volume +, Volume - repeat.  The others do not, except for
> >   the rather special Switch window key.  Upon press it produces
> >   the LAlt-down, LShift-down, Tab-down, Tab-up sequence; it
> >   repeats Tab-down; and upon release it produces the sequence
> >   Tab-up, LAlt-up, LShift-up.
> > (Up events are as usual for the other 17 keys.)

Vojtech Pavlik wrote:
> The code as is now (with the autorepeat and the forced up if the
> keyboard itself doesn't start repeating) won't have any problems with
> this keyboard.

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.

Unfortunately, not doing the forced-up thing causes much worse
problems, with the keys which started this thread.

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.

That gives perfect results for typing, and after the first press of a
key it is perfect for games too.

-- Jamie


> 
> -- 
> Vojtech Pavlik
> SuSE Labs, SuSE CR
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/