Re: [gtk-vnc-devel] [PATCH][RFC] Support for ExtendedKeyEvent client message
- From: Markus Armbruster <armbru redhat com>
- To: Anthony Liguori <anthony codemonkey ws>
- Cc: gtk-vnc-devel List <gtk-vnc-devel lists sourceforge net>
- Subject: Re: [gtk-vnc-devel] [PATCH][RFC] Support for ExtendedKeyEvent client message
- Date: Mon, 21 Jan 2008 18:11:50 +0100
Anthony Liguori <anthony codemonkey ws> writes:
> Markus Armbruster wrote:
>> Anthony Liguori <anthony codemonkey ws> writes:
>>
>>
>>> Not really. PC key codes are well defined for one type of keyboard,
>>> but are used by every keyboard. I guess there's a 1-1 mapping of
>>> Linux keycodes to PC keycodes. I don't believe Linux keycodes are
>>> richer than PC key codes though because PC key codes are what are
>>> being generated from the actual keyboard. By definition, there has to
>>> be a PC key code for any given key while this isn't necessarily true
>>> for Linux keycodes.
>>>
>>
>> There has to be a PC key code for every physical key on a PC keyboard.
>>
>> However, not every keyboard is a PC keyboard, and some of them have
>> keys that that don't exist on PC keyboards.
>>
>
> Well, I think this is our problem. When I say, PC key code, I don't
> mean the codes assigned to keys on a PC101 keycode. I mean any
> hardware keycode that is delivered through a PS/2 port.
>
> GDK calls this a "hardware keycode" which is perhaps a better nomenclature.
>
> Regards,
>
> Anthony Liguori
Is this code at least as rich as the Linux input layer code? If not,
is it rich enough for all practical purposes?
Where is this code defined?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]