From: Erik Rull <erik.rull@rdsoftware.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Trouble with numlock and SDL
Date: Sun, 26 Apr 2015 14:12:13 +0200 [thread overview]
Message-ID: <553CD61D.3070708@rdsoftware.de> (raw)
In-Reply-To: <1429774344.26641.15.camel@nilsson.home.kraxel.org>
Hi Gerd,
it seems to be a bug sitting in front of the computer :-)
I just recompiled the new SDL and didn't recompile QEMU against the new SDL
- I recognized later that there are version dependent pieces of code in QEMU.
I will proceed my tests on this topic on other systems, I will send an
update when the results are available.
Best regards,
Erik
Gerd Hoffmann wrote:
> On Mi, 2015-04-22 at 18:20 +0200, Erik Rull wrote:
>> Hi all,
>>
>> I'm struggling a bit with the numlock state when using SDL.
>> On SDL 1.2.13 I have the problem that the numlock state is inverted for QEMU -
>> but it is switchable.
>
> Move focus out of sdl window -- hit numlock once -- move focus back in.
> Does that synchronize things?
>
> Is this something new? IIRC there have been no (intentional) changes in
> that area recently.
>
>> On SDL 1.2.14 and 1.2.15 I can't enable the number input in any state of the
>> numlock key.
>
> No idea on that one. Sounds like SDL not sending numlock key events at
> all.
>
>> With VNC everything is fine.
>
> Yep. vnc has some special logic to sync guest/host numlock state (also
> for capslock). Maybe we should factor that out into reusable helper
> functions.
>
> cheers,
> Gerd
>
>
>
next prev parent reply other threads:[~2015-04-26 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 16:20 [Qemu-devel] Trouble with numlock and SDL Erik Rull
2015-04-23 7:32 ` Gerd Hoffmann
2015-04-26 12:12 ` Erik Rull [this message]
2015-04-27 10:53 ` Erik Rull
2015-04-27 11:13 ` Gerd Hoffmann
2015-10-19 16:02 ` Erik Rull
2015-10-20 7:54 ` Gerd Hoffmann
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=553CD61D.3070708@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=kraxel@redhat.com \
--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.