From: Programmingkid <programmingkidx@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-trivial <qemu-trivial@nongnu.org>,
"qemu-devel qemu-devel" <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] Adds the ability to use the command key in the guest operating system.
Date: Wed, 14 Aug 2013 21:31:56 -0400 [thread overview]
Message-ID: <13863120-443B-4B80-939C-543A8216EF01@gmail.com> (raw)
In-Reply-To: <B8F69B83-8EC9-4337-99BF-B18B84CB7531@suse.de>
On Aug 14, 2013, at 4:58 PM, Alexander Graf wrote:
>
> On 14.08.2013, at 22:52, Peter Maydell wrote:
>
>> On 14 August 2013 21:44, Anthony Liguori <anthony@codemonkey.ws> wrote:
>>> I'm confident there's a way to get hardware keycodes on OS X. There
>>> is on every other UI platform that I know of. That's the best way to
>>> solve this.
I know you want to use hardware keycodes, but here are (IMHO) the reasons why we should stick with the PC/XT layout:
1) Simple - only one keyboard layout to deal with.
2) Compatible - This layout works with operating systems from MS-DOS 1.0 to Ubuntu Linux 12.
3) Less work - no major code changes.
4) Good enough - does work with Mac OS X.
5) Would Mac keyboard keycodes work with Windows, AIX, Solaris, and OS/2? Doubt it. Guess which keyboard layout would work.
>>
>> Sure, but that doesn't answer the fundamental question of "when
>> should the OS's window/menu accelerator operate the OS menu and
>> when should it be passed to the guest as a raw key". However you
>> get the keycodes you still have that choice.
>
> The normal rule of thumb IIRC is when mouse grab is active, everything goes into the guest.
That is a good idea. I am thinking of eliminating the -command-key option and just doing the above suggestion.
Anybody else have their own idea for solving the command key issue?
prev parent reply other threads:[~2013-08-15 1:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 22:52 [Qemu-devel] [PATCH v2] Adds the ability to use the command key in the guest operating system G 3
2013-08-03 23:06 ` Peter Maydell
2013-08-03 23:43 ` Programmingkid
2013-08-04 9:39 ` Peter Maydell
2013-08-04 11:58 ` Anthony Liguori
2013-08-04 18:22 ` Programmingkid
2013-08-04 17:53 ` Programmingkid
2013-08-04 18:07 ` Peter Maydell
2013-08-04 18:52 ` Programmingkid
2013-08-14 18:02 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2013-08-14 20:44 ` Anthony Liguori
2013-08-14 20:52 ` Peter Maydell
2013-08-14 20:58 ` Alexander Graf
2013-08-15 1:31 ` Programmingkid [this message]
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=13863120-443B-4B80-939C-543A8216EF01@gmail.com \
--to=programmingkidx@gmail.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@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).