From: John Max Skaller <skaller@ozemail.com.au>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: checker@d6.com, caml-list@inria.fr
Subject: Re: labltk bind ~events list questions/bugs?
Date: Wed, 03 Jan 2001 11:07:01 +1100 [thread overview]
Message-ID: <3A526D25.4743C8EC@ozemail.com.au> (raw)
In-Reply-To: <20001231165106J.garrigue@kurims.kyoto-u.ac.jp>
Jacques Garrigue wrote:
>
> From: Chris Hecker <checker@d6.com>
> > 2. As another question, if I have ~events:[`Modified
> > ([`Shift],`KeyPress)], sometimes I just get the keys that were pressed
> > when the shift key was down, sometimes I get a zillion Shift_L events,
> > and sometimes I get nothing.
>
> Stranger. This should be only the first case. At least, this is how it
> works on X11.
Here's my guess: this is a 'quirk' of the PC keyboard firmware.
It is a serious problem for game design. What happens is that
when there are NO keys pressed, and you press any repeating key,
you get a sequence of KEY_DOWN tokens from the keyboard.
If you then press another key, the auto-repeat is switched OFF
for the first key, and on for the second key. If you release
the second key, the first doesn't auto-repeat:
11111111111111122222222222222
^ press 1 ....^ press 2 ^ release 2 ^ release 1
aaaaaaaaaaaaaaaaa
^ press a ^ press shift
The _only_ solution is to reprogram the keyboard CPU.
The whole thing is a stupid hangover from DOS: the keyboard
should just send keyup/keydown tokens, and let the OS driver
handle repeats and timing.
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net
next prev parent reply other threads:[~2001-01-03 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 8:01 Chris Hecker
2000-12-31 7:51 ` Jacques Garrigue
2001-01-03 0:07 ` John Max Skaller [this message]
2000-12-31 20:25 ` John Max Skaller
2001-01-03 14:29 ` Vladimir Vyskocil
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=3A526D25.4743C8EC@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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;
as well as URLs for NNTP newsgroup(s).