Bug Tracker – Bug 1187

certain keys not working

Last modified: 2016-11-11 22:03:32 CST
Bug 1187 - (ARRAY(0x61644c0)) certain keys not working
(ARRAY(0x61644c0))
certain keys not working
Status: NEW
Product: Odamex
Classification: Unclassified
Component: Client
0.7.x
All All
: P1 normal
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2016-09-17 18:54:51 CDT by Russell Rice
Modified: 2016-11-11 22:03 CST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russell Rice 2016-09-17 18:54:51 CDT
Keys such as caps lock, scroll lock and num lock do not work while in game. for example we have a default bind to toggle cl_run to capslock

Another is the Print Screen/SysRq button, which is used for generating screenshots. This does not work while in game and it also creates a "lag" effect on the game loop if held down
Comment 1 Dr. Sean 2016-09-25 18:32:27 CDT
This appears to break in trunk with r5371, where the inputabs branch was merged into trunk.
Comment 2 Dr. Sean 2016-09-26 23:36:18 CDT
The key binding system used hard-coded SDL key codes for associating key name strings (such as "bind capslock +jump") instead of the codes defined in doomkeys.h. 

There are still some keys without codes defined in doomkeys.h which will need to be assigned codes before this can be closed:
    F13, F14, F15, numlock, lwin, rwin, help, sysrq, break
Comment 3 Dr. Sean 2016-09-27 21:52:48 CDT
r5487 should address these issues. Please test the PrintScreen/SysRq issue specifically though.
Comment 4 Russell Rice 2016-09-28 00:12:16 CDT
in r5487 it would not work, r5488 works but instead of being sysrq, it is now print if the screenshot key is rebound in the options menu
Comment 5 Ralph Vickers 2016-11-11 22:03:32 CST
Tested this on 24889a9 and can confirm that all of those assigned codes work but printscreen/sysrq is not bindable from the customize controls menu