On Sat, 22 Nov 2008 13:49:42 +0100 Marc Weustink <[EMAIL PROTECTED]> 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 Mattias _______________________________________________ Lazarus mailing list [email protected] http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
