All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bug in SDL key event processing
Date: Thu, 10 Jul 2008 17:03:23 -0500	[thread overview]
Message-ID: <4876872B.6080704@codemonkey.ws> (raw)
In-Reply-To: <20080710215524.GB4579@implementation>

Samuel Thibault wrote:
> Anthony Liguori, le Thu 10 Jul 2008 14:25:05 -0500, a écrit :
>   
>>> Keep in mind that using '-k' completely changes the semantics of the 
>>> keyboard. I'm using the colemak layout, so my top row is: qwfpg. For 
>>> the sake of simplicity, assume that the guest uses the standard en-us 
>>> layout.
>>>       
>> Then you would need to add a colemak translation table if you wanted 
>> that to be reflected in the guest.  However, if you use -k en-us and use 
>> en-us in the guest, it should just work for you.
>>     
>
> 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 '!'...

Yes, unfortunately, I don't see a great way to fix that :-/  You 
basically have to have the guest also set up to use azerty.

>  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..
>   

Which is what we're trying to do.  The issue is that the 
keysyms=>positional keycode mapping is 1->many.  That's what the -k 
mappings are selecting.

Regards,

Anthony Liguroi

> Samuel
>
>
>   

  reply	other threads:[~2008-07-10 22:03 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 [this message]
2008-07-10 22:14                             ` Samuel Thibault
2008-07-14 16:02                           ` Ian Jackson
2008-07-14 16:27                             ` Samuel Thibault
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=4876872B.6080704@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.