I didn't know about the hardware key codes. Since it works everywhere,
could it be possible to have that in the default config file in SVN,
because it solves the azerty problem !
They uses the same key codes, but the implementation are different.
Yours is easier and shorter.
Bruno
2009/9/16 "Jérôme M. Berger" <jeber...@free.fr>:
> Bruno Vernay wrote:
>>
>> So, I tested the proposed solutions.
>>
>> - first mapping the tag_keys =
>> {"&","#11",'"',"'","(","-","#16","_","#18"} as they appear on an
>> azerty keyboard and then uses tag_key[i] instead of i.
>>
>> - second, uses tag_keys = { '#10', '#11', '#12', '#13', '#14', '#15',
>> '#16', '#17', '#18' } I don't understand why "&" == "#10", but it
>> works.
>>
>> - Finally, the jeber...@free.fr 's one doesn't require a tag_key array
>> and should works with qwerty ?! But I don't see why ("#1"..i-1) would
>> give the same result as (i) ???
>>
> Actually, the second solution and mine are the same. The code
> ("#1"..i-1) means successively "#10", "#11", ... and "#18". The reason why
> this should work on any type of keyboard is that those numbers are the
> *hardware* key codes and therefore they refer to the actual position of the
> key on the keyboard rather than to the symbol printed on the key.
>
> You can get the hardware key code associated with any key with the
> "xev" program.
>
> Jerome
> --
> mailto:jeber...@free.fr
> http://jeberger.free.fr
> Jabber: jeber...@jabber.fr
>
>
--
Bruno VERNAY
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
