From: Helge Hafting <helgehaf@aitel.hist.no>
To: Nicolas Mailhot <Nicolas.Mailhot@laposte.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Fri, 26 Sep 2003 15:56:42 +0200 [thread overview]
Message-ID: <3F74459A.7060903@aitel.hist.no> (raw)
In-Reply-To: 1064581715.23200.9.camel@ulysse.olympe.o2t
Nicolas Mailhot wrote:
[...]
> I wrote about monster autorepeats not every single duplicated keypress.
> I fully agree it's stupid to expect detecting every single bogus repeat.
>
> However saying the system has no way to guess monster
> autorepeats=problem is just plain wrong. There *are* thresholds after
> which one can be 99% sure there is a problem (autorepeat gone mad or cat
> sitting on the keyboard). No one is going to complain he has to release
> a key every hundred or so repeats to confirm there's a human on the
> other side of the keyboard.
>
First, such detection is kind of useless. If I get 200 W's before
the system detects, well I'll fix it long before detection kicks
in by tapping the stuck key. That tends to unstick it.
Keys don't usually get stuck when nobody's there, they stick because
of a missed release, not a bogus press.
Second - yes, people are going to get impressively pissed off
if they have to release a key now and then. Scrolling on a heavily
loaded machine - it stops from time to time anyway - but now we
have to release the key all the time?
And don't even think of having to release a key now and then in
a action game. Games may use any key, so no restriction on
which keys may repeat is useable.
Gamers press keys for a long time, movement keys in quake, the
accelerator key in a car game, the fire key in space invaders.
Bogus unsticking of keys isn't acceptable - there will certainly
be a storm of patches for removing the misfeature.
Helge Hafting
next prev parent reply other threads:[~2003-09-26 13:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 9:43 Keyboard oddness Nicolas Mailhot
2003-09-26 10:24 ` Vojtech Pavlik
2003-09-26 10:41 ` Nicolas Mailhot
2003-09-26 10:51 ` Vojtech Pavlik
2003-09-26 12:48 ` jw schultz
2003-09-26 13:08 ` Nicolas Mailhot
2003-09-26 13:41 ` Vojtech Pavlik
2003-09-26 14:12 ` Nicolas Mailhot
2003-09-26 14:17 ` Vojtech Pavlik
2003-09-26 14:21 ` Nicolas Mailhot
2003-09-26 14:26 ` Vojtech Pavlik
2003-09-26 14:50 ` Nicolas Mailhot
2003-09-26 15:06 ` Vojtech Pavlik
2003-09-26 15:21 ` Nicolas Mailhot
2003-09-26 15:24 ` Vojtech Pavlik
2003-09-26 13:56 ` Helge Hafting [this message]
2003-09-26 14:01 ` Mike Dresser
2003-09-28 10:58 ` Helge Hafting
2003-10-02 12:40 ` Pavel Machek
2003-10-01 10:09 ` Pavel Machek
2003-10-01 13:06 ` Nicolas Mailhot
-- strict thread matches above, loose matches on Subject: below --
2003-09-20 20:33 Rob Landley
2003-09-20 22:18 ` Andries Brouwer
2003-09-21 18:51 ` Rob Landley
2003-09-21 10:04 ` Vojtech Pavlik
2003-09-21 20:20 ` Rob Landley
2003-09-22 20:06 ` Rob Landley
2003-09-22 22:06 ` Andries Brouwer
2003-09-23 0:23 ` Rob Landley
2003-09-23 10:51 ` Greg Louis
2003-09-25 23:59 ` Rob Landley
2003-09-26 1:27 ` Rob Landley
2003-09-26 8:15 ` Andries Brouwer
2003-09-26 8:43 ` Rob Landley
2003-09-26 8:46 ` Vojtech Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F74459A.7060903@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=Nicolas.Mailhot@laposte.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox