From: Juan Quintela <quintela@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 4/4] kbd keds: vnc
Date: Thu, 25 Feb 2010 12:03:12 +0100 [thread overview]
Message-ID: <m3zl2xpogf.fsf@trasno.mitica> (raw)
In-Reply-To: <1267087161-15204-5-git-send-email-kraxel@redhat.com> (Gerd Hoffmann's message of "Thu, 25 Feb 2010 09:39:21 +0100")
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Use led status notification support in vnc.
> +static void kbd_leds(void *opaque, int ledstate)
> +{
> + VncState *vs = opaque;
> + int caps, num;
> +
> + caps = ledstate & QEMU_CAPS_LOCK_LED ? 1 : 0;
> + num = ledstate & QEMU_NUM_LOCK_LED ? 1 : 0;
I think it is clearer to use a bool.
bool caps = ledstate & QEMU_CAPS_LOCK_LED;
> + if (vs->modifiers_state[0x3a] != caps) {
> + vs->modifiers_state[0x3a] = caps;
modifiers_state type needs to go from uint8_t to bool. It simplifies
lots of !!foo around. But the change is independent of this series.
> + }
> + if (vs->modifiers_state[0x45] != num) {
> + vs->modifiers_state[0x45] = num;
> + }
> +}
> +
> static void do_key_event(VncState *vs, int down, int keycode, int sym)
> {
> /* QEMU console switch */
> @@ -1521,7 +1538,7 @@ static void do_key_event(VncState *vs, int down, int keycode, int sym)
> break;
> case 0x3a: /* CapsLock */
> case 0x45: /* NumLock */
> - if (!down)
> + if (down)
> vs->modifiers_state[keycode] ^= 1;
> break;
> }
This needs a comment on the changelog why this is needed IMHO.
Later, Juan.
next prev parent reply other threads:[~2010-02-25 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 8:39 [Qemu-devel] [PATCH 0/4] keyboard led status tracking Gerd Hoffmann
2010-02-25 8:39 ` [Qemu-devel] [PATCH 1/4] kbd leds: infrastructure Gerd Hoffmann
2010-02-25 10:57 ` [Qemu-devel] " Juan Quintela
2010-02-25 14:15 ` [Qemu-devel] " Anthony Liguori
2010-02-25 14:36 ` Gerd Hoffmann
2010-02-25 15:07 ` Anthony Liguori
2010-02-25 16:51 ` Gerd Hoffmann
2010-02-25 17:05 ` Anthony Liguori
2010-02-25 8:39 ` [Qemu-devel] [PATCH 2/4] kbd leds: ps/2 kbd Gerd Hoffmann
2010-02-25 10:59 ` [Qemu-devel] " Juan Quintela
2010-02-25 8:39 ` [Qemu-devel] [PATCH 3/4] kbd leds: usb kbd Gerd Hoffmann
2010-02-25 8:39 ` [Qemu-devel] [PATCH 4/4] kbd keds: vnc Gerd Hoffmann
2010-02-25 11:03 ` Juan Quintela [this message]
2010-02-25 11:11 ` [Qemu-devel] " Paolo Bonzini
2010-02-26 16:05 ` Gerd Hoffmann
2010-02-28 1:38 ` [Qemu-devel] " Paul Brook
2010-03-01 8:12 ` 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=m3zl2xpogf.fsf@trasno.mitica \
--to=quintela@redhat.com \
--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.