It seems my openMSX has problems with my Alt Gr key...
Unfortunatly my keyboard has the square brackets [ ] accessible only through Alt Gr and i seem unable to make openMSX see them.
Anyone got an idea about how i could fix this?
Can you enable the keyboard trace logging?
TO do so, open the console with F10 and type: set kbd_trace_key_presses on
Then try to type the symbols with Alt-Gr (like [ and ]) and paste the output of the logging. (Probably ends up in the Catapult Output tab, or in the command prompt window.)
The command is accepted without error but i can't see any log generated by that command.
Catapult doesn't show anything, in any tab i can see, stdout and stderr are empty and no file seems to be generated in the openMSX folder or the user-data openMSX folder...
Please double check for typos. (Hint use tab-completion, so type 'set kbd_tr[tab] on'). If this step went correct you should get a response 'true' from openMSX. Next close the openMSX console (press F10) again. And start typing in e.g. MSX-BASIC. The logging information should appear on stdout. When you started openMSX from catapult this should appear in one of the tabs. If you started openMSX manually from a command prompt, the logging should appear there.
You are correct, sorry for being this stupid... i kept typing "pressed" instead of "presses" in the command that Manuel suggested me... i typed it so many times and never noticed it... the autocompletition helped figure it out... thanx.
This is the log i can now see on stdout/stderr when i click ALTGR+[:
Key pressed, unicode: 0x0000, keyCode: 0x00132, keyName: LCTRL
Key pressed, unicode: 0x0000, keyCode: 0x40133, keyName: RALT+CTRL
Key pressed, unicode: 0x005b, keyCode: 0xc005b, keyName: LEFTBRACKET+CTRL+ALT
Key released, unicode: 0x0000, keyCode: 0x4c005b, keyName: LEFTBRACKET+CTRL+ALT,
RELEASE
Key released, unicode: 0x0000, keyCode: 0x480132, keyName: LCTRL+ALT,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400133, keyName: RALT,RELEASE
I don't understand why it sees LCTRL, CTRL and ALT....
This is what happens when i only click once ALTGR:
Key pressed, unicode: 0x0000, keyCode: 0x00132, keyName: LCTRL
Key pressed, unicode: 0x0000, keyCode: 0x40133, keyName: RALT+CTRL
Key released, unicode: 0x0000, keyCode: 0x480132, keyName: LCTRL+ALT,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400133, keyName: RALT,RELEASE
Thanx.
Anyways... for now i kind of fixed the problem with:
bind F6 "keymatrixdown 1 0x20"
bind F6,release "keymatrixup 1 0x20"
bind F7 "keymatrixdown 1 0x40"
bind F7,release "keymatrixup 1 0x40"
but of course i would very much prefer to have my ALTGR key working...
I have tried with Belgium Azert keyboard which also has [ and ] only available with alt-gr key. Under linux (openSuSE 13.1) it works fine. I get following output from kbd_trace=true when I enter [:
RMODE is the logical code for the alt-gr key
the [ character is on the same key as the caret (^) character, which is the second press; CARET+MODE
After that, CARET+MODE get first released and then RMODE gets released.
I notice in the windows output that you posted above that apparently Windows or SDL on Windows is not recognizing the alt-gr key as the RMODE code but as LCTRL together zith RALT (left control key + right alt key)
Unfortunately I don't have Windows 7 but I do have Windows Vista. I'll try openMSX under Vista and then post here another comment with the findings.
It's more probably a Windows 7/8 problem. If you use Google with 'AltGr not working", you'll get many results!
On blueMSX, the problem can also happen (I've a Belgian AZERTY keyboard), and the solution seems to choose temporarily as Language preference English (USA) with English USA keyboard layout. You need to go in the Config Panel to add this "2nd" language (and an icon in the traybar will be useful to switch from one language to another one).
