qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com, aliguori@amazon.com, lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH] ui/input: correct the release order of combined keys
Date: Fri, 26 Sep 2014 15:44:40 +0800	[thread overview]
Message-ID: <1411717480-31299-1-git-send-email-akong@redhat.com> (raw)

Commit 2e377f17 wrongly overturned the release order of combined keys,
it caused some Windows guests can't be paniced by "virsh send-key
<domain> KEY_RIGHTCTRL KEY_SCROLLLOCK KEY_SCROLLLOCK"

The press event order should be different with release order.

Signed-off-by: Amos Kong <akong@redhat.com>
---
 ui/input-legacy.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/ui/input-legacy.c b/ui/input-legacy.c
index 3025f50..1e1f14c 100644
--- a/ui/input-legacy.c
+++ b/ui/input-legacy.c
@@ -85,16 +85,23 @@ void qmp_send_key(KeyValueList *keys, bool has_hold_time, int64_t hold_time,
                   Error **errp)
 {
     KeyValueList *p;
+    int count, i;
 
     if (!has_hold_time) {
         hold_time = 0; /* use default */
     }
 
+    count = 0;
     for (p = keys; p != NULL; p = p->next) {
         qemu_input_event_send_key(NULL, copy_key_value(p->value), true);
         qemu_input_event_send_key_delay(hold_time);
+        count++;
     }
-    for (p = keys; p != NULL; p = p->next) {
+    while (count--) {
+        i = 0;
+        for (p = keys; p != NULL && i < count; p = p->next) {
+            i++;
+        }
         qemu_input_event_send_key(NULL, copy_key_value(p->value), false);
         qemu_input_event_send_key_delay(hold_time);
     }
-- 
1.9.3

                 reply	other threads:[~2014-09-26  7:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1411717480-31299-1-git-send-email-akong@redhat.com \
    --to=akong@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@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 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).