From: Peter Maydell <peter.maydell@linaro.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v5 3/4] adb-keys.h: initial commit
Date: Tue, 15 Mar 2016 17:43:55 +0000 [thread overview]
Message-ID: <CAFEAcA8iXgcoiueDsM4=LxvkwqXf39xTtaFH86qn0drHY_42nA@mail.gmail.com> (raw)
In-Reply-To: <E7C32AB3-032F-49FB-8318-19D8AB0C9AA9@gmail.com>
On 15 March 2016 at 17:17, Programmingkid <programmingkidx@gmail.com> wrote:
> This commit implements the adb-keys.h file. It holds information on adb keycode
> values.
>
> Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
> ---
> * v5 changes
> +/*
> + * adb-keys.h
> + *
> + * Provides an enum of all the Macintosh keycodes.
> + * Note: keys like Power, volume related, and eject are handled at a lower
> + * level and are not available to QEMU. That doesn't mean we can't
> + * substitute one key for another. The function keys like F1 make a good
> + * substitute for these keys. This can be done in the GTK, SDL, or Cocoa
> + * code.
> + * Additional information: http://www.archive.org/stream/apple-guide-macintosh
> + * -family-hardware/Apple_Guide_to_the_Macintosh_Family
> + * _Hardware_2e#page/n345/mode/2up - page 308
Better to have the whole URL on one line so you can just cut-n-paste
it into a web browser.
> + ADB_KEY_LEFT_CONTROL = 54,
> + ADB_KEY_RIGHT_CONTROL = 125,
> + ADB_KEY_LEFT_OPTION = 58,
> + ADB_KEY_RIGHT_OPTION = 124,
> + ADB_KEY_LEFT_COMMAND = 55,
> + ADB_KEY_RIGHT_COMMAND = 126,
Where does this one come from? The Apple doc shows the Extended Keyboard
as generating the same keycode for left and right command (0x37).
(Incidentally if we're using that doc as our official reference for
the keycodes then using hex the same as it does would be good.)
thanks
-- PMM
next prev parent reply other threads:[~2016-03-15 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 17:17 [Qemu-devel] [PATCH v5 3/4] adb-keys.h: initial commit Programmingkid
2016-03-15 17:43 ` Peter Maydell [this message]
2016-03-15 18:02 ` Programmingkid
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='CAFEAcA8iXgcoiueDsM4=LxvkwqXf39xTtaFH86qn0drHY_42nA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--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).