[Lazarus] gtk2 warning

Marc Weustink marc at dommelstein.net
Sat Nov 22 14:43:32 CET 2008

Mattias Gaertner wrote:
> On Sat, 22 Nov 2008 13:49:42 +0100
> Marc Weustink <marc at dommelstein.net> wrote:
>> Paul Ishenin wrote:
>>> Mattias Gaertner wrote:
>>>> I get this at every start:
>>>> [WARNING] Out of OEM specific VK codes, changing to unassigned
>>>> [WARNING] Out of unassigned VK codes, assigning $FF
>>>> Is this known?
>>> I see them too. Is that something bad?
>> Yes, this is bad. It means that some keypresses wont get reported
>> anymore.
>> Each key reported by X should get a VK_xxx number assigned to report
>> to the LCL. Based on some lookups, an attempt is made to asign a VK
>> which is "constant" between widgetsets and is compatible with windows
>> (and thus the VCL and thus the LCL). As a result of this the "A" key
>> gets the VK_A and the "F5" key VK_F5 etc. However problems arise for
>> other keys like the ones with "[]\;',./-=" For known combos, a
>> VK_OEM_ value is assigned (see lcltype.pp for combos). Based on a
>> Microsoft keyboard layout tool, I covered most combos.
>> When no existing VK_ value can be found, values from the unassinged 
>> range are assigned first, then from the reserved range and then just
>> $FF since there are no more values to choose from.
>> I wonder what keyboard layouts generate this.
> ubuntu 8.10, layout USA, generic 105-key(intl) PC

Weird, I'm using a generic 105-key. Maybe the (intl) makes the 
difference. Can you sent me the output of xmodmap -pk ?


More information about the Lazarus mailing list