From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/4] kbd leds: infrastructure
Date: Tue, 09 Mar 2010 17:41:44 +0100 [thread overview]
Message-ID: <4B967A48.5030005@redhat.com> (raw)
In-Reply-To: <4B96771B.5020509@codemonkey.ws>
On 03/09/10 17:28, Anthony Liguori wrote:
> If a person has a guest that twiddles with LEDs, what are the chances
> they are going to figure out that there's an option with VNC to not use
> LED status as part of the modifier tracking heuristics?
>
> I don't think it's really useful. Like I said in an earlier note, we're
> already dealing with a heuristics based algorithm because we're
> attempting to detect dangling modifier presses. I'd rather see an option
> that disabled the whole thing verses something specific to the LEDs.
You are referring to the
do-i-should-insert-extra-capslock/numlock-events logic in do_key_event()
? Well, we can turn off both, fine with me, after all they sort-of
belong together. Do you have an idea for a short
'no-capslock-and-numlock-tracking-heuristics' option name?
cheers,
Gerd
next prev parent reply other threads:[~2010-03-09 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 16:17 [Qemu-devel] [PATCH v2 0/4] keyboard led status tracking Gerd Hoffmann
2010-02-26 16:17 ` [Qemu-devel] [PATCH v2 1/4] kbd leds: infrastructure Gerd Hoffmann
2010-03-09 15:02 ` Anthony Liguori
2010-03-09 15:58 ` Paul Brook
2010-03-09 16:09 ` Anthony Liguori
2010-03-09 16:13 ` Gerd Hoffmann
2010-03-09 16:28 ` Anthony Liguori
2010-03-09 16:41 ` Gerd Hoffmann [this message]
2010-03-09 17:10 ` Anthony Liguori
2010-02-26 16:17 ` [Qemu-devel] [PATCH v2 2/4] kbd leds: ps/2 kbd Gerd Hoffmann
2010-02-26 16:17 ` [Qemu-devel] [PATCH v2 3/4] kbd leds: usb kbd Gerd Hoffmann
2010-02-26 16:17 ` [Qemu-devel] [PATCH v2 4/4] kbd keds: vnc Gerd Hoffmann
2010-02-26 17:29 ` [Qemu-devel] Re: [PATCH v2 0/4] keyboard led status tracking Juan Quintela
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=4B967A48.5030005@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=paul@codesourcery.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 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).