Keymappings may not be universal

[notwopr]

When Anya tried SEM Apprentice v2.1 - noscreenshot version, the keymappings were not the same as mine. For example, a key she pressed on the numpad return an unaccounted for mapping: <255>. causing an error in the log.

Is this just because the num lock was off? I noticed keycodes with the following form of "<"integer number">" are only for certain keys. In my case they are the following: "<12>": "numpad_numlockoff_5", "<48>": "ctrl_0", "<49>": "ctrl_1", "<50>": "ctrl_2", "<51>": "ctrl_3", "<52>": "ctrl_4", "<53>": "ctrl_5", "<54>": "ctrl_6", "<55>": "ctrl_7", "<56>": "ctrl_8", "<57>": "ctrl9", "<186>": "ctrl;", "<222>": "ctrl_'", "<188>": "ctrl_comma", "<190>": "ctrl_period", "<191>": "ctrl_forwardslash", "<187>": "ctrl_equal", "<189>": "ctrl_minus", "<192>": "ctrl_backtick", "<96>": "numpad_numlockon_0", "<97>": "numpad_numlockon_1", "<98>": "numpad_numlockon_2", "<99>": "numpad_numlockon_3", "<100>": "numpad_numlockon_4", "<101>": "numpad_numlockon_5", "<102>": "numpad_numlockon_6", "<103>": "numpad_numlockon_7", "<104>": "numpad_numlockon_8", "<105>": "numpad_numlockon_9", "<106>": "numpad_ctrl_asterisk", "<107>": "numpad_ctrl_plus", "<109>": "numpad_ctrl_minus", "<110>": "numpad_numlockon_period", "<111>": "numpad_ctrl_forwardslash",

[notwopr]

So do keycodes of the form do they occupy the same keys universally or not? Do keycodes occupy keys that are normally of another form on a different keyboard? Is there a more reliable keycode method that is static across all keyboards or most keyboards using U.S. English keyboard layout?

[notwopr]

look for a python library that resolves this.