From: Amos Kong <akong@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, aliguori@amazon.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] ui/input: fix event emitting of repeated combined keys
Date: Wed, 29 Oct 2014 15:12:51 +0800 [thread overview]
Message-ID: <20141029071251.GA30477@air.redhat.com> (raw)
In-Reply-To: <1411981796.32643.13.camel@nilsson.home.kraxel.org>
On Mon, Sep 29, 2014 at 11:09:56AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > It doesn't matter, so users might release the modifier key or not.
> > we should make both works
> >
> > 1)
> > sendkey Ctrl-Scroll
> > sendkey Ctrl-Scroll
>
> Good to know this works.
>
> > 2)
> > sendkey Ctrl-Scroll-Scroll
>
> Why?
Quote from http://msdn.microsoft.com/en-us/library/windows/hardware/ff545499(v=vs.85).aspx
The keyboard crash can be initiated by using the following hotkey
sequence: _Hold down_ the rightmost CTRL key, and press the SCROLL LOCK
key twice.
> This tries to squeeze something into the sendkey interface which
> it doesn't was designed for, and IMO this isn't a good idea, especially
> if we have something better at hand (marcelos patch).
My patch fixed this problem, but it's a hack. Marcelo's patch works in
(press/release) event level, it's more clear.
Thanks.
> cheers,
> Gerd
>
--
Amos.
next prev parent reply other threads:[~2014-10-29 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 10:23 [Qemu-devel] [PATCH v2] ui/input: fix event emitting of repeated combined keys Amos Kong
2014-09-26 10:36 ` Gerd Hoffmann
2014-09-26 10:53 ` Amos Kong
2014-09-26 11:24 ` Gerd Hoffmann
2014-09-26 15:15 ` Marcelo Tosatti
2014-09-29 8:59 ` Gerd Hoffmann
2014-09-27 3:29 ` Amos Kong
2014-09-29 9:09 ` Gerd Hoffmann
2014-10-29 7:12 ` Amos Kong [this message]
2014-09-26 14:04 ` Eric Blake
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=20141029071251.GA30477@air.redhat.com \
--to=akong@redhat.com \
--cc=aliguori@amazon.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mtosatti@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.