From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PULL 4/7] ui: add multimedia keys
Date: Fri, 28 Jul 2017 09:28:26 +0100 [thread overview]
Message-ID: <20170728082826.GE31495@redhat.com> (raw)
In-Reply-To: <1501222909.10943.1.camel@redhat.com>
On Fri, Jul 28, 2017 at 08:21:49AM +0200, Gerd Hoffmann wrote:
> On Thu, 2017-07-27 at 18:45 +0100, Daniel P. Berrange wrote:
> > On Thu, Jul 27, 2017 at 04:00:22PM +0200, Gerd Hoffmann wrote:
> > > Add multimedia keys to QKeyCodes and to the keymaps.
> > >
> > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > > Reviewed-by: Eric Blake <eblake@redhat.com>
> > > Message-id: 20170726152918.11995-5-kraxel@redhat.com
> > > ---
> > > ui/input-keymap.c | 44
> > > ++++++++++++++++++++++++++++++++++++++++++++
> > > qapi-schema.json | 28 +++++++++++++++++++++++++++-
> > > 2 files changed, 71 insertions(+), 1 deletion(-)
> > >
> > I'm curious what the 'AC_' prefix on all these is indicating ?
> > Do we actually need it ?
>
> Seems to stand for "application control".
>
> # grep " AC " include/standard-headers/linux/input-event-codes.h
> * AC - Application Control
> #define KEY_STOP 128 /* AC Stop */
> #define KEY_PROPS 130 /* AC Properties */
> #define KEY_UNDO 131 /* AC Undo */
> [ ... ]
>
> I think it is better to keep it, even if it is inconsistent because we
> already have stop + find without prefix. Just dropping the ac_ prefix
> will not work for some keys, ac_home for example.
Ok
>
> > Missing Q_KEY_CODE_MEDIASELECT entry - presumably it was supposed
> > to map to KEY_MEDIA
>
> There is KEY_SELECT too, but not KEY_MEDIASELECT. Hmm.
I found a keyboard with a key labelled "Media" and when pressed
it generates Linux key 171 / AT set1 0xe0 0x01 which is KEY_CONFIG
and GNOME pops up the control panel when pressed !
Would be interested to know results of "showkey" and "showkey -s" for
any other keyboards with a key labelled "Media", since I don't entirely
trust this particular one to be representative of general usage.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-07-28 8:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 14:00 [Qemu-devel] [PULL 0/7] Ui 20170727 patches Gerd Hoffmann
2017-07-27 14:00 ` [Qemu-devel] [PULL 1/7] ui: add next and prior keysyms Gerd Hoffmann
2017-07-27 14:00 ` [Qemu-devel] [PULL 2/7] ui: move qemu_input_linux_to_qcode() Gerd Hoffmann
2017-07-27 14:00 ` [Qemu-devel] [PULL 3/7] ui: update keymaps Gerd Hoffmann
2017-07-27 14:00 ` [Qemu-devel] [PULL 4/7] ui: add multimedia keys Gerd Hoffmann
2017-07-27 17:45 ` Daniel P. Berrange
2017-07-28 6:21 ` Gerd Hoffmann
2017-07-28 8:28 ` Daniel P. Berrange [this message]
2017-07-28 9:57 ` Gerd Hoffmann
2017-07-28 10:01 ` Daniel P. Berrange
2017-07-27 14:00 ` [Qemu-devel] [PULL 5/7] ps2: enable " Gerd Hoffmann
2017-07-27 14:00 ` [Qemu-devel] [PULL 6/7] ui: drop altgr and altgr_r QKeyCodes Gerd Hoffmann
2017-07-27 14:00 ` [Qemu-devel] [PULL 7/7] ps2: fix sending of PAUSE/BREAK scancodes Gerd Hoffmann
2017-07-27 14:02 ` Daniel P. Berrange
2017-07-27 15:43 ` [Qemu-devel] [PULL 0/7] Ui 20170727 patches Peter Maydell
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=20170728082826.GE31495@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@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.