qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Amon <amon@stanfordalumni.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mac keyboard not supported
Date: Tue, 28 Dec 2004 13:26:54 +0100	[thread overview]
Message-ID: <1104236814.41d1510ecf637@imp2-q.free.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0412281251060.9471@wgmdd8.biozentrum.uni-wuerzburg.de>

Selon Johannes Schindelin <Johannes.Schindelin@gmx.de>:

> Hi,
>
> On Tue, 28 Dec 2004, Laurent Amon wrote:
>
> > On 28 déc. 04, at 02:16, Johannes Schindelin wrote:
> > >

> What are the messages for 1..0?

Can't tell you right now, I am at work. It is a mix of accented characters,
symbols and numbers. Some characters do appear twice.
>
> > I hacked a workable keyboard (or rather enhanced on a hack Johannes
> > Fortmann wrote) in july (posted to the list on july 17th and 21st) but
> > I'd rather build on the current system.
>
> You should, as the only way to support different keyboard layouts for
> other platforms than a PC would be to duplicate the work.

I should... what? Build through a new keymap or add code for the support of
other keyboard. I am not clear on the meaning of your sentence.
>
> > I guess that the mac keycodes are different from te PC ones and need an
> > extra translation. SDL is not perfect in that respect, though I haven't
> > tries 1.2.8 release.
>
> That aspect didn't change AFAIK. Anyway, the keycodes may differ, but
> *not* the keysyms. The whole purpose of keysyms *is* that they are
> platform-independent. If they are not correct on the Mac, then SDL has to
> be fixed.

My old patch did that, by providing extra transcoding. SDL seems to work
correctly when you are not changing platforms, but here we are trying to
emulate a PC keyboard under windows when the hardware is a Apple keyboard under
OSX. I can't expand more since I haven't studied the 0.6.1 code and I don't have
my machine at hand right now.

Rgds,

Lga.

  reply	other threads:[~2004-12-28 12:38 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 [this message]
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
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=1104236814.41d1510ecf637@imp2-q.free.fr \
    --to=amon@stanfordalumni.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 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).