From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding more function keys support
Date: Wed, 13 Dec 2017 09:14:58 +0000 [thread overview]
Message-ID: <20171213091458.GA28379@redhat.com> (raw)
In-Reply-To: <11216FAC-3F62-43AF-ACD8-00F28B7AD886@gmail.com>
On Tue, Dec 12, 2017 at 12:49:34PM -0500, Programmingkid wrote:
>
> > On Dec 12, 2017, at 9:34 AM, Daniel P. Berrange <berrange@redhat.com> wrote:
> >
> > On Sun, Dec 10, 2017 at 02:10:41AM -0500, Programmingkid wrote:
> >> On Macintosh keyboards there is a key called fn that is used to give the
> >> function keys more functionality. Does this key exist in the keyboard keys
> >> database?
> >
> > When you say "Macintosh keyboards" are you talking about the old style
> > keyboards with Apple's custom ADB connector, or simply Apple branded
> > USB keyboards ?
>
> USB keyboards.
>
> >
> > If its the latter (USB), then please plug it into a Linux machine, and
> > in a text console (ie not X11) run 'showkey' and press this 'fn' key on
> > its own and tell me what (if any) hex code gets printed.
>
> There was no response to the fn key.
Doh, I made a mistake - you need to run 'showkey -s' to get raw scancodes.
Can you try this again, pressing 'fn' on its own, and also press 'fn' in
combination with some function keys.
> >> Also could keys F16 to F24 (Q_KEY_CODE_F16 to Q_KEY_CODE_F24) be added to
> >> the database?
> >
> > Those are already defined in keycodemapdb, so we just need to give them
> > names in the qapi schema, and then add the name mapping to keycodemapdb.
>
> I have a vague memory of doing something like this a long time ago.
> Hopefully I can find the path if it exists.
In qapi/ui.json you need to edit the enum 'QKeyCode' to define the
extra keys.
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-12-13 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 7:10 [Qemu-devel] Adding more function keys support Programmingkid
2017-12-12 14:34 ` Daniel P. Berrange
2017-12-12 17:49 ` Programmingkid
2017-12-13 9:14 ` Daniel P. Berrange [this message]
2017-12-13 16:03 ` Programmingkid
2017-12-13 18:22 ` BALATON Zoltan
2017-12-13 19:18 ` Programmingkid
2017-12-14 2:20 ` Eric Blake
2017-12-14 2:23 ` Programmingkid
2017-12-14 10:27 ` Daniel P. Berrange
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=20171213091458.GA28379@redhat.com \
--to=berrange@redhat.com \
--cc=programmingkidx@gmail.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).