From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: simultaneous keys
Date: Sun, 09 Feb 2003 21:29:09 +0300 [thread overview]
Message-ID: <3E469DF5.7080006@yahoo.com> (raw)
Hello.
Jan Willem Stumpel wrote:
>> Do you mean the keys must be kept pressed in order it to stay
>> on screen?
> No, also if you keep both keys pressed SK disappears.
I am asking how it intended to work.
Is it enough to just release the shift
keys to make it disappear, or it is
necessary to press something to make
it go away?
I have tested it with xev: if I hold
the left shift and press the right
shift, X generates 3 events (Press,
Release, Press) instead of 1 (Press)
in most cases and only sometimes it
generates a single event. The same is
with release, but again only when the
left shift is being pressed.
Is it true also for you?
> xdosemu, X_keycode is auto (default) in dosemu.conf.
How good does it work with other
settings? console/raw? $_X_keycode=(off)?
next reply other threads:[~2003-02-09 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 18:29 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-09 16:38 simultaneous keys Stas Sergeev
2003-02-09 17:44 ` Jan Willem Stumpel
2003-02-09 15:12 Jan Willem Stumpel
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=3E469DF5.7080006@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@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