From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mac keyboard not supported
Date: Mon, 17 Jan 2005 23:08:02 +0100 [thread overview]
Message-ID: <41EC3742.8000307@bellard.org> (raw)
In-Reply-To: <1105980688.41ebed104f3b5@imp4-q.free.fr>
For the problem of the Mac keyboard, I think SDL should be fixed first
to return correct SDL keysyms.
An interesting patch was submitted some time ago to use the scan codes
directly, as we do on PCs (scan codes do not depend on the keyboard key
mapping). If it is reported to work on most Macs, it should be the
default because it avoids the problem of translating keysyms to scan codes.
Fabrice.
Laurent Amon wrote:
> Hi,
>
> Selon Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>
>
>>I don't think the SDL guys are slow. And it is no major rework. It is one
>>file, one function, and if I'm correct, just deletion of 3 lines -- and it
>>should be a lot easier than replicating a whole keymap.
>
> If you can point me to the 3 lines, I'll try to compile SDL and see if it works
> better. I hope I'll have a moment to look at it in the next few days. Not my
> priority, though.
>
>
>>For normal users, there is no need to differentiate between left and right
>>modifier keys. Also, it is not important to have exactly the same mapping
>>as on PC, but only that if you hit a key (e.g. '/') that the guest
>>actually understands the same key ('/'). No more, no less.
>
> I don't agree with you. When you type '/', the guest OS needs to to know the
> keycode corresponding to the '/' on the keyboard you emulate as well as the
> modifier key mask necessary to generate it. I believe windows works on that
> level, does it not? I don't think that you can simply pass the character.
> As to differenciating between left/right keys, it would be handy in order to
> emulate a Alt-Graph key (which is needed since qemu now grabs ctrl-alt), and
> the "contextual menu" key too. Not to mention playing pinball.
>
>
>>[...] And yes, unless the good SDL people
>>decide to release (after a patch was sent to them), you'd have to
>>distribute a patched SDL (which would of course, being patcheed, break all
>>apps using SDL -- NOT!).
>
> As you point out, it would probably not break anything. It is just extra
> logistics.
>
> Bye,
>
> Lga.
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
next prev parent reply other threads:[~2005-01-17 22:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 16:40 [Qemu-devel] Mac keyboard not supported Laurent Amon
2004-12-27 18:36 ` Phil Krylov
2004-12-28 1:16 ` Johannes Schindelin
2004-12-28 7:29 ` Laurent Amon
2004-12-28 11:55 ` Johannes Schindelin
2004-12-28 12:26 ` Laurent Amon
2004-12-28 12:41 ` Johannes Schindelin
2004-12-29 5:13 ` Natalia Portillo
2005-01-01 18:20 ` Laurent Amon
2005-01-02 14:40 ` Phil Krylov
2005-01-02 16:24 ` Laurent Amon
2005-01-02 17:47 ` Phil Krylov
2005-01-02 19:22 ` Johannes Schindelin
2005-01-02 20:16 ` Laurent Amon
2005-01-17 15:01 ` Johannes Schindelin
2005-01-17 16:51 ` Laurent Amon
2005-01-17 17:58 ` Johannes Schindelin
2005-01-17 22:08 ` Fabrice Bellard [this message]
2005-01-17 23:17 ` Laurent Amon
2005-01-17 17:54 ` David Still
2005-01-17 18:42 ` Johannes Schindelin
2005-01-17 19:33 ` Laurent Amon
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=41EC3742.8000307@bellard.org \
--to=fabrice@bellard.org \
--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.