From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Peter Lieven <lieven@dlhnet.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vnc: lift modifier keys on client disconnect.
Date: Mon, 17 Jun 2013 14:09:06 +0200 [thread overview]
Message-ID: <51BEFC62.6080109@redhat.com> (raw)
In-Reply-To: <51BEED6D.7000008@dlhnet.de>
On 06/17/13 13:05, Peter Lieven wrote:
> Am 17.06.2013 10:49, schrieb Gerd Hoffmann:
>> On 06/17/13 10:10, Peter Lieven wrote:
>>> Hi Gerd,
>>>
>>> just looking at your patch. It works fine so far, but I am curious how
>>> to handle the lock keys? I have the problem that if I press caps lock
>>> and then create a new vnc session with exclusive access (from another
>>> terminal), the caps lock is still there.
>>
>> There is some logic for that in the vnc server, next time you press a
>> letter key it should get synced up. capslock+numlock can actually
>> easier go out of sync than the other modifiers, you don't need a
>> reconnect to trigger that: Activate some other window so the vnc client
>> window so it hasn't the keyboard focus, press capslock or numlock, move
>> focus back to the vnc window.
>
> It seems the sync logic fails iff.
> Caps Lock enabled -> VNC Disconnect -> Caps Lock disabled -> VNC Reconnect.
> In this case the guest OS is still typing uppercase letters.
I guess reset_keys() should skip capslock+numlock to not disturb the
sync logic, can you try that?
cheers,
Gerd
next prev parent reply other threads:[~2013-06-17 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 12:28 [Qemu-devel] [PATCH] vnc: lift modifier keys on client disconnect Gerd Hoffmann
2013-06-17 8:10 ` Peter Lieven
2013-06-17 8:49 ` Gerd Hoffmann
2013-06-17 11:05 ` Peter Lieven
2013-06-17 12:09 ` Gerd Hoffmann [this message]
2013-06-17 13:20 ` Peter Lieven
2013-06-17 13:58 ` Gerd Hoffmann
2013-06-17 15:38 ` Peter Lieven
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=51BEFC62.6080109@redhat.com \
--to=kraxel@redhat.com \
--cc=lieven@dlhnet.de \
--cc=pl@dlhnet.de \
--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.