Oy!
I’m running Lucid and I installed EDuke32 and Mapster32 with the official APT repos.
I have a pretty annoying issue with my keyboard (full-size USB QWERTY). So far the following keys just won’t work in Mapster32:
` [ ] \ . /
I thus cannot make slopes in the editor or automatically pan tiles. These keys won’t work in JonoF’s Build either. I can type those characters in the map’s filename though. When configuring the keys in EDuke32, they are recognized as numbers.
Can anyone help me? I could not find any answer on the web.
Page 1 of 1
Build/Mapster keys not working under Linux
#1 Posted 24 November 2010 - 01:43 PM
#2 Posted 24 November 2010 - 02:31 PM
Its posible to remap (Change) your keys, open mapster32.cfg in notepad to make the changes, go to the bottom and see the instructions.
Example.
remap = 10-3A,52-4C,53-B8
Example.
remap = 10-3A,52-4C,53-B8
#3 Posted 24 November 2010 - 02:50 PM
And after you've made those changes to the cfg file, change the property of the file to "read only" so it won't change the keys every time you launch mapster.
This post has been edited by Forge: 24 November 2010 - 02:51 PM
#4 Posted 24 November 2010 - 04:04 PM
Wow thanks that worked!
Could you tell me which keys are not used in Mapster32? I wouldn’t like my keys to overlap.
Could you tell me which keys are not used in Mapster32? I wouldn’t like my keys to overlap.
#5 Posted 25 November 2010 - 09:54 AM
i changed my keys too because of the stupid numlock button setup thing thing. but the only keys that i remember that i changed right now is REnter-RCtrl. then some of the num lock keys that streches the tiles. i think it is originally numlock 2-4-6-8. 2 and 8 being opposites and 4 and 6 being opposites.
#6 Posted 01 December 2010 - 01:12 PM
To the OP:
this really seems like a misconfiguration of X (or the keyboard part) to me. The way I understand it is than X effectively adds another translation stage to the keys that is moreover visible to the application. This is unlike Windows, where raw keycodes seem to be passed to it. Are you running a non-US keyboard layout by chance? It could be as simple as that.
Fixes for various other issues:
* AltGr
* dead key cominations like Shift-KP5-KP8/2
* needs solution: caps lock if it's remapped to Ctrl...
this really seems like a misconfiguration of X (or the keyboard part) to me. The way I understand it is than X effectively adds another translation stage to the keys that is moreover visible to the application. This is unlike Windows, where raw keycodes seem to be passed to it. Are you running a non-US keyboard layout by chance? It could be as simple as that.
Fixes for various other issues:
* AltGr
* dead key cominations like Shift-KP5-KP8/2
* needs solution: caps lock if it's remapped to Ctrl...
Share this topic:
Page 1 of 1