qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bug in SDL key event processing
Date: Mon, 14 Jul 2008 17:27:51 +0100	[thread overview]
Message-ID: <20080714162751.GX4466@implementation.uk.xensource.com> (raw)
In-Reply-To: <18555.30890.637466.506702@mariner.uk.xensource.com>

Ian Jackson, le Mon 14 Jul 2008 17:02:50 +0100, a écrit :
> Samuel Thibault writes ("Re: [Qemu-devel] Bug in SDL key event processing"):
> > That won't for the shifted characters. Let's take for instance azerty,
> > which has the numbers in the shifted position instead of the direct
> > position. Typing shift+1 will produce a 1 keysym, which will indeed be
> > converted to the correct scancode, but shift will be simulated too, and
> > thus produce in the guest '!'... There is no other correct than properly
> > reverse-engineering the keysyms we get into a positional keycode, and
> > then convert to PS2 scancode, and let the guest use its keymaps..
> 
> Well, one alternative approach would be to simulate a shift down
> event, followed by the key in question, followed by a shift up event.

Uuuggghh (to say the least).

Even more tricky.  I have an azerty keyboard.  To type '\' I press
alt-gr + '8'.  Qemu receives a '\' keysym, with altgr being pressed.
How do you know that that alt-gr is to be dropped (because it's an
artifact of the azerty keyboard) or kept as is (in the qwerty case one
may want to have an alt-gr + '\' shortcut)?

Samuel

  reply	other threads:[~2008-07-14 16:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 23:27 [Qemu-devel] Bug in SDL key event processing Tomas Carnecky
2008-07-09 23:37 ` Samuel Thibault
2008-07-09 23:46   ` Tomas Carnecky
2008-07-09 23:55     ` Samuel Thibault
2008-07-10  0:09       ` Tomas Carnecky
2008-07-10  0:20         ` Samuel Thibault
2008-07-10  3:19         ` Anthony Liguori
2008-07-10  7:56           ` Tomas Carnecky
2008-07-10 13:35             ` Anthony Liguori
2008-07-10 13:43               ` Tomas Carnecky
2008-07-10 13:56                 ` Anthony Liguori
2008-07-10 14:03                 ` Tomas Carnecky
2008-07-10 14:10                   ` Samuel Thibault
2008-07-10 14:20                     ` Tomas Carnecky
2008-07-10 14:49                       ` Samuel Thibault
2008-07-10 14:39                   ` Anthony Liguori
2008-07-10 15:35                     ` Tomas Carnecky
2008-07-10 15:51                       ` Samuel Thibault
2008-07-10 19:25                       ` Anthony Liguori
2008-07-10 19:51                         ` Tomas Carnecky
2008-07-10 21:55                         ` Samuel Thibault
2008-07-10 22:03                           ` Anthony Liguori
2008-07-10 22:14                             ` Samuel Thibault
2008-07-14 16:02                           ` Ian Jackson
2008-07-14 16:27                             ` Samuel Thibault [this message]
2008-07-14 16:01                         ` Ian Jackson
2008-07-09 23:52   ` Anthony Liguori
2008-07-10 12:03     ` Jamie Lokier
2008-07-10 12:24       ` Samuel Thibault
  -- strict thread matches above, loose matches on Subject: below --
2008-07-10 14:22 Juergen Keil

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=20080714162751.GX4466@implementation.uk.xensource.com \
    --to=samuel.thibault@ens-lyon.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).