Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2008-11

gtk2 warning

8 messages · 6 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mattias Gaertner

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?

Mattias

Reply by email

Paul Ishenin
to Mattias Gaertner
Mattias Gaertner wrote 8 lines
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?

Best regards,
Paul Ishenin.

Reply by email

Marc Weustink
to Paul Ishenin
Paul Ishenin wrote 10 lines
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.

Marc

Reply by email

Mattias Gaertner
to Marc Weustink
Show quoted text 28 lines
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

Mattias

Reply by email

Micha Nelissen
to Mattias Gaertner
Mattias Gaertner wrote 5 lines
On Sat, 22 Nov 2008 13:49:42 +0100 Marc Weustink wrote: > I wonder what keyboard layouts generate this. ubuntu 8.10, layout USA, generic 105-key(intl) PC

That's very exotic indeed :P

Micha

Reply by email

Marc Weustink
to Mattias Gaertner: On Sat, 22 Nov 2008 13:49:42 +0100 ubuntu 8.10, layout USA, generic 105-key(intl) PC…
Mattias Gaertner wrote 32 lines
On Sat, 22 Nov 2008 13:49:42 +0100 Marc Weustink 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 ?

Marc

Reply by email

Lord Satan
to Marc Weustink: Weird, I'm using a generic 105-key. Maybe the (intl) makes the difference. Can you sent…
Yes, this is bad. It means that some keypresses wont get reported anymore.

Anything happening on this front?
I keep getting this message and other people, too, as you can see by searching the mailing list for it. Strange thing is that I could not find the mantis issue corresponding to this. Is there any bug report?

S.

A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?

Reply by email