#59 numeric keys not working in fuse 0.10.0.2 for Czech keyboard

[Anonymous]

I have a problem which I cant solve. I compiled 0.10.0.2 with SDL UI but numeric keys do not produce any reaction in fuse. All alpha characters work fine as well as special keys. This is on Mandriva 2009.1 KDE4 environment - dont know if it may have relevance. The same happens with the default PLF 0.10.0.2 gtk build.

[Fredrick Meunier]

Fuse doesn't support using the numeric keypad for input, the extra key codes would need to be added to keysyms.dat and keysyms.pl.

[Nobody/Anonymous]

I did not mean the numeric keypad, but the keys with numbers - the keyboard row beneath the function keys and above the "qwertyuiop" - this is supposed to work, isnt it? This prevents me from starting many games as it requires pressing "1", "2" etc...

[Nobody/Anonymous]

OK - thanks for pointing me in the right direction. It turned out that fuse runs with default keyboard layout, which has numbers on the original positions but with a shift button pressed (cz locale) - which is a problem in fuse. The current keyboard layout of KDE is not taken into account - "setxkbmap us && fuse" does the trick.

[Fredrick Meunier]

Right I see, yes Fuse only works with QWERTY keyboard layouts. In order to work generically there would need to be one of a couple of approaches:
a) overlay a UK keyboard on whatever the real keyboard is - the key that would hold 1 on a UK layout will produce 1 etc. - need to know which key codes in the keyboard matrix correspond to which physical position on the keyboard, makes most sense for games with key layouts based on the physical layout on a UK machine (e.g. QAOP+SPACE)
b) whatever the symbol in the locale is is presented to the underlying machine - e.g. SHIFT+1 in AZERTY == 1 key for Spectrum - need to know the key symbol produced for a given keypress, doesn't play well with Spectrum BASIC symbol shift and extended modes

[Fredrick Meunier]

Should be fixed for GTK in revision 4116.

[Gergely Szasz]

We should reopen this ticket, because never fixed. (revision 5706)... or see: [feature-requests:#101]

[SourceForge Robot]

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).