From: Gerd Hoffmann <kraxel@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: Xen-devel@lists.xensource.com,
Junko Ichino <ichino.junko@jp.fujitsu.com>
Subject: Re: [RFC] keymap support for PVFB
Date: Fri, 12 Jan 2007 12:02:56 +0100 [thread overview]
Message-ID: <45A76AE0.2040701@suse.de> (raw)
In-Reply-To: <87bql4ed1n.fsf@pike.pond.sub.org>
Markus Armbruster wrote:
>>> Passing scan codes in addition to key symbols makes sense.
>> Does the vnc protocol allow that? I don't think so :-(
>
> Broken as designed...
>
> Your hack has the advantage that you don't configure the client keymap
> into the server, and therefore don't have to kick the server whenever
> the client keymap changes.
Yep. You can even connect two clients with different local keymaps and
it still works ;)
> But when your client receives a funky key
> that ordinary US keyboards don't have, you don't have the key symbol
> for it.
That is exactly the drawback ...
> Hmm, can we make one up then? I mean it's a hack to begin with, why
> not put another hack on top of it? As long as every key gets its own
> key symbol, and the made-up ones don't screw up servers that don't
> know of this hack...
We can try that. For the 102th/105th key on i18n keyboards we likely
have to create something. For the extra keys the japanese keyboards
have we maybe can simply send the existing keysyms for these keys
(assuming the scancodes for these keys are unique, i.e. used on japanese
keyboards only).
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-01-12 11:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 4:11 [RFC] keymap support for PVFB Junko Ichino
2006-12-28 16:02 ` Ewan Mellor
2007-01-09 0:56 ` Kasai Takanori
2007-01-09 1:07 ` Junko Ichino
2007-01-10 20:18 ` Markus Armbruster
2007-01-11 9:09 ` Gerd Hoffmann
2007-01-11 17:53 ` Markus Armbruster
2007-01-12 8:15 ` Gerd Hoffmann
2007-01-12 10:48 ` Markus Armbruster
2007-01-12 11:02 ` Gerd Hoffmann [this message]
2007-01-12 12:16 ` Daniel P. Berrange
2007-01-11 14:09 ` Junko Ichino
2007-01-11 17:54 ` Markus Armbruster
2007-01-17 6:07 ` Junko Ichino
2007-01-17 7:48 ` Markus Armbruster
2007-01-17 9:39 ` Junko Ichino
2007-01-17 10:21 ` Markus Armbruster
2007-01-17 11:39 ` Junko Ichino
2007-01-17 12:46 ` Kasai Takanori
2007-01-17 13:25 ` Markus Armbruster
2007-01-18 12:17 ` Junko Ichino
2007-01-18 15:01 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2007-01-12 12:35 Bruce Rogers
2007-01-12 13:32 ` Daniel P. Berrange
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=45A76AE0.2040701@suse.de \
--to=kraxel@suse.de \
--cc=Xen-devel@lists.xensource.com \
--cc=armbru@redhat.com \
--cc=ichino.junko@jp.fujitsu.com \
/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.