For example, if I press X along with a shift layer button and try to let go of both buttons at once, I might let go of the shift layer button first by accident, and that causes X to send both the shift layer mapping and the regular mapping. Is there a way to make the shift layer "eat" the button input, so that it can't send another mapping after sending the shifted one? Thanks!
Announcement
Collapse
No announcement yet.
Help with sending accidental inputs using shift layer
Collapse
X
-
Originally Posted by Shion View PostSolution here would be to disable [Preferences > General > Re-press the held button when switching Shift layers] option.
- Flag
Comment
-
Originally Posted by reWASDer View PostIt should work for all layers. Could you please describe the exact order of buttons you press and hold?
- Hold down shift 1 (left upper paddle)
- Hold down X, which has both a main config and shift 1 mapping
- Release shift 1
This sends both the main config mapping and the shift 1 mapping, even with the re-press feature disabled.
- Flag
Comment
-
Hmm. We were able to reproduce this issue and will fix it with the next update (6.1.2, ETA - start of May).
For now a temporary solution would be to have all buttons that remapped differently on other Shifts, remapped to themselves on [ Main Shift] with [Mute] flag enabled for them like in the config attached.Attached Files
- Flag
Comment
-
Originally Posted by Shion View PostHmm. We were able to reproduce this issue and will fix it with the next update (6.1.2, ETA - start of May).
For now a temporary solution would be to have all buttons that remapped differently on other Shifts, remapped to themselves on [ Main Shift] with [Mute] flag enabled for them like in the config attached.
- Flag
- Likes 1
Comment
Comment