From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9mQO-0004rZ-G4 for qemu-devel@nongnu.org; Wed, 14 Aug 2013 21:32:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9mQJ-00015L-Bf for qemu-devel@nongnu.org; Wed, 14 Aug 2013 21:32:28 -0400 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Programmingkid In-Reply-To: Date: Wed, 14 Aug 2013 21:31:56 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <13863120-443B-4B80-939C-543A8216EF01@gmail.com> References: <358B0F62-7043-432E-8B49-F95CD1B82443@gmail.com> <9A748A2F-42CF-4600-AE57-5B013DBC02F2@gmail.com> <2A318D54-11AD-4C05-B5A3-54F35E906571@gmail.com> Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] Adds the ability to use the command key in the guest operating system. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Peter Maydell , qemu-trivial , qemu-devel qemu-devel , "qemu-ppc@nongnu.org list:PowerPC" , Anthony Liguori , =?iso-8859-1?Q?Andreas_F=E4rber?= On Aug 14, 2013, at 4:58 PM, Alexander Graf wrote: >=20 > On 14.08.2013, at 22:52, Peter Maydell wrote: >=20 >> On 14 August 2013 21:44, Anthony Liguori = 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.=20 3) Less work - no major code changes. 4) Good enough - does work with Mac OS X.=20 5) Would Mac keyboard keycodes work with Windows, AIX, Solaris, and = OS/2? Doubt it. Guess which keyboard layout would work. >>=20 >> 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. >=20 > 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.=20 Anybody else have their own idea for solving the command key issue?=20=