Opened 8 years ago
Last modified 8 years ago
#4521 closed defect
Hotkeys in user.cfg will not set properly — at Initial Version
| Reported by: | am2del | Owned by: | |
|---|---|---|---|
| Priority: | Should Have | Milestone: | |
| Component: | UI & Simulation | Keywords: | |
| Cc: | Patch: |
Description
Build: 27 Feb 2017 (18915P-release) installed on Linux, kernel: 4.10.5-1, x86_64 architecture.
When setting hotkeys from within the user.cfg, default hotkeys are overridden properly according to log - however, defined hotkeys are unset in-game.
I.e.: In user.cfg: hotkey.selection.group.select.0 = 0 ...will show properly in log, but in-game "0" will no longer select a group. hotkey.selection.group.select.0 = "A" ...will show properly in log, but neither "A" nor "0" will select no group.
Issue seems to affect ALL hotkeys if set through the user.cfg. Using individual or group paths makes no difference either; i.e.: [hotkey.selection.group.select] 0 = 0 ...will yield same as above examples.
Copy-pasting full set of hotkeys from default.cfg to user.cfg will disable ALL keyboard hotkeys. (Issue does not seem to affect mousebuttons.)
NOTE: Hotkey settings aside, everything seems to work fine through the user.cfg, and since it shows properly in log the issue is likely in the "set clause" for hotkeys. I.e. set "A" as hotkey for "hotkey.selection.group.select.0" and log will inform "A" is the hotkey read from user.cfg, but won't select the group and default key (in this case "0") stops working aswell, so it clearly overrides the default without setting new key - or setting "NONE".
