From: Akihiko Odaki <akihiko.odaki@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Konstantin Nazarov <mail@knazarov.com>,
qemu-devel@nongnu.org, Akihiko Odaki <akihiko.odaki@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH v2] ui/cocoa: Comment about modifier key input quirks
Date: Fri, 12 Mar 2021 00:12:03 +0900 [thread overview]
Message-ID: <20210311151203.21902-1-akihiko.odaki@gmail.com> (raw)
Based-on: <20210310042348.21931-1-akihiko.odaki@gmail.com>
Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
---
ui/cocoa.m | 32 +++++++++++++++++++++++++++++++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/ui/cocoa.m b/ui/cocoa.m
index 035f96aab04..3d292269c11 100644
--- a/ui/cocoa.m
+++ b/ui/cocoa.m
@@ -700,13 +700,35 @@ - (bool) handleEventLocked:(NSEvent *)event
NSPoint p = [self screenLocationOfEvent:event];
NSUInteger modifiers = [event modifierFlags];
- // emulate caps lock keydown and keyup
+ /*
+ * If -[NSEvent modifierFlags] has NSEventModifierFlagCapsLock,
+ * toggle the current CapsLock state by firing "up" and "down" events in
+ * sequence.
+ */
if (!!(modifiers & NSEventModifierFlagCapsLock) !=
qkbd_state_modifier_get(kbd, QKBD_MOD_CAPSLOCK)) {
qkbd_state_key_event(kbd, Q_KEY_CODE_CAPS_LOCK, true);
qkbd_state_key_event(kbd, Q_KEY_CODE_CAPS_LOCK, false);
}
+ /*
+ * Check for other flags of -[NSEvent modifierFlags].
+ *
+ * If a flag is not set, fire "up" events for all keys which correspond to
+ * the flag. Note that "down" events are not fired here because the flags
+ * checked here do not tell what exact keys are down.
+ *
+ * These operations are performed for any events because the modifier state
+ * may change while the application is inactive (i.e. no events fire) and
+ * we want to detect it as early as possible.
+ *
+ * Up events corresponding to a modifier flag update the current modifier
+ * state tracked with QKbdState but they are not fired unless all keys which
+ * match to the flag are up. Therefore, it cannot synchornize Cocoa and
+ * QkbdState if one of the keys is down. It is still nice that any
+ * desynchronization can be fixed by completely leaving your hands from the
+ * keyboard.
+ */
if (!(modifiers & NSEventModifierFlagShift)) {
qkbd_state_key_event(kbd, Q_KEY_CODE_SHIFT, false);
qkbd_state_key_event(kbd, Q_KEY_CODE_SHIFT_R, false);
@@ -726,6 +748,14 @@ - (bool) handleEventLocked:(NSEvent *)event
switch ([event type]) {
case NSEventTypeFlagsChanged:
+ /*
+ * If the state of the key corresponding to -[NSEvent keyCode] is
+ * not updated by checking -[NSEvent modifierFlags], update it here.
+ * It means -[NSEvent keyCode] does not represent CapsLock and
+ * the corresponding modifier flag is set.
+ * [self toggleKey] peeks QkbdState so it correctly works only when
+ * it is synchornized with Cocoa.
+ */
switch ([event keyCode]) {
case kVK_Shift:
if (!!(modifiers & NSEventModifierFlagShift)) {
--
2.24.3 (Apple Git-128)
next reply other threads:[~2021-03-11 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 15:12 Akihiko Odaki [this message]
2021-03-12 10:19 ` [PATCH v2] ui/cocoa: Comment about modifier key input quirks Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2021-03-12 13:32 Akihiko Odaki
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=20210311151203.21902-1-akihiko.odaki@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=kraxel@redhat.com \
--cc=mail@knazarov.com \
--cc=peter.maydell@linaro.org \
--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).