From: Gerd Hoffmann <kraxel@redhat.com>
To: Ian McKellar <ianloic@google.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling
Date: Wed, 24 May 2017 08:17:27 +0200 [thread overview]
Message-ID: <1495606647.30747.10.camel@redhat.com> (raw)
In-Reply-To: <CA+YAiviJq3VSLR1yCD9Yob7xb5z60Gw59mrSLL1+qFrtnv7OUw@mail.gmail.com>
Hi,
> After a little more experimentation I think that the approach in this
> patch is the right one. modifierFlags doesn't[1] indicate which
> instance of a modifier (ie: left or right) is being held.
Ok, makes sense. One more thing: I think capslock must be handled
differently as keydown + keyup toggle state.
cheers,
Gerd
next prev parent reply other threads:[~2017-05-24 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 18:02 [Qemu-devel] [PATCH 1/1] Improve Cocoa modifier key handling Ian McKellar
2017-05-23 10:03 ` Gerd Hoffmann
2017-05-23 15:52 ` Ian McKellar
2017-05-23 17:39 ` Ian McKellar
2017-05-24 6:17 ` Gerd Hoffmann [this message]
2017-05-26 23:39 ` Ian McKellar
[not found] <mailman.71687.1494691106.22739.qemu-devel@nongnu.org>
2017-05-18 0:23 ` G 3
-- strict thread matches above, loose matches on Subject: below --
2017-05-12 22:25 Ian McKellar
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=1495606647.30747.10.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=ianloic@google.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).