From: Programmingkid <programmingkidx@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Command-line option to change ungrab key(s)
Date: Mon, 13 Nov 2017 09:29:25 -0500 [thread overview]
Message-ID: <03123F70-98FA-439A-868C-855E63916259@gmail.com> (raw)
Would you accept a patch that allows the user to change the mouse ungrab key(s) in QEMU?
It would look something like this:
-ungrab <key>
or
-ungrab <key>,<key>,...
If the user wanted the F19 key to be the ungrab key, this is what would be sent to QEMU:
-ungrab F19
If the user wanted F16 and F17 held down to ungrab the mouse, this is what would be sent to QEMU:
-ungrab F16,F17
Would this feature be something you would consider adding to QEMU?
next reply other threads:[~2017-11-13 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 14:29 Programmingkid [this message]
2017-11-13 14:31 ` [Qemu-devel] Command-line option to change ungrab key(s) Peter Maydell
2017-11-13 14:50 ` Daniel P. Berrange
2017-11-13 15:20 ` Marc-André Lureau
2017-11-13 15:27 ` Programmingkid
2017-11-14 7:21 ` Gerd Hoffmann
2017-11-14 13:47 ` Programmingkid
2017-11-14 14:00 ` 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=03123F70-98FA-439A-868C-855E63916259@gmail.com \
--to=programmingkidx@gmail.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).