View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0003074 | Spring engine | General | public | 2012-04-28 04:39 | 2012-04-28 04:39 | ||||||||
Reporter | luckywaldo7 | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | new | Resolution | open | ||||||||||
Product Version | 88.0 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0003074: uikeys behavior "bug" | ||||||||||||
Description | Supposing I made some keybinds like: bind f fight bind shift+f fight bind f attack bind shift+f attack So I have two different commands attached to the same hotkey, with "fight" being defined first. Generally, spring is pretty smart about this, and lets me toggle between them by tapping the hotkey. However, instead of going in the order I bind, when I press 'f' it defaults first to 'attack' and then second to 'fight'. If I press 'shift+f' for a queued command, it uses the right order, defaulting to fight and then switching to attack on the next press. Also, buildunit keybinds always seem to work in the correct order. The only time it seems to not work right is a standard command with no modifiers. As far as I can tell it seems to cycle through the commands alphabetically, instead of using the uikeys order. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Checked infolog.txt for Errors | |||||||||||||
Attached Files |
|
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2012-04-28 04:39 | luckywaldo7 | New Issue |