Thanks Hermann and Paul for clarifying this to me. I didn't noticed the difference to *the keysdown*
You say Apple changed the keyboard mapping. I have no idea, if and how this could affect now LC 8 concerning backward compatibility with older systems. Will the keysdown give me on "all" systems (from 10.8-10.12) the same codes, if Apple changed something in any system? Can I rely on this workaround to get the correct chars, which have been entered on "all" systems? Has anybody a best guest on how to handle this? Tiemo P.S. yes I filed it in the QC -----Ursprüngliche Nachricht----- Von: use-livecode [mailto:[email protected]] Im Auftrag von hh Gesendet: Montag, 5. Dezember 2016 23:27 An: [email protected] Betreff: Re: Is there a mapping table for all rawKeyUp Codes? No solution yet with LC 8 Hi all. Yes that's the point: *The keysDown* return the correct (hardware) keyCode. Tiemo is right, there is a bug introduced around LC 8. From the dictionary: "The keycodes returned by the keysDown function are the same as those passed as parameters with the rawKeyDown and rawKeyUp messages." That's not true (I tested with all latest versions of LC 8.1.1 and up and Paul confirmed for some). Thus we can possibly locate the bug: Apple changed his keyboard mapping method around the introduction of LC 8 (it is no longer in easy accessible files but in "layout bundles"). Was _the keysDown_ adjusted by the LC-team and _rawkeyDown/Up_ not? Tiemo, you should definitely report this!? _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
