x11: add KP_Separator to key mapping

At least on some keyboards, the key between '0' and 'Enter' on the
key pad is mapped to KP_Separator. Since X11 VOs accept unicode
input, the mplayer keycode this key generates depended on the numlock
state, and with numlock enabled this mapped to an ASCII character.
This is probably not what the user wanted, since two physical keys
will always map to the same key code.

Map it to KP_DEC.
This commit is contained in:
wm4 2012-01-13 08:25:21 +01:00
parent e722967580
commit 10ab86b73d
2 changed files with 2 additions and 0 deletions

View File

@ -56,6 +56,7 @@
#define wsEscape 0xff1b
#define wsGrayEnter 0xff8d
#define wsGrayPlus 0xffab
#define wsGraySeparator 0xffac
#define wsGrayMinus 0xffad
#define wsGrayMul 0xffaa
#define wsGrayDiv 0xffaf

View File

@ -564,6 +564,7 @@ static const struct mp_keymap keymap[] = {
{wsGray3, KEY_KP3}, {wsGray4, KEY_KP4}, {wsGray5, KEY_KP5},
{wsGray6, KEY_KP6}, {wsGray7, KEY_KP7}, {wsGray8, KEY_KP8},
{wsGray9, KEY_KP9}, {wsGrayDecimal, KEY_KPDEC},
{wsGraySeparator, KEY_KPDEC},
// numpad without numlock
{wsGrayInsert, KEY_KPINS}, {wsGrayEnd, KEY_KP1}, {wsGrayDown, KEY_KP2},