-
-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the input mapping system to not dispatch both a matched KeyDown and KeyDownNoRepeat #2266
Comments
Can I have a go at this? |
You're welcome to give it a try, sure. Just be aware that it is likely only something that can be successfully completed by someone with a good level of software engineering experience, since it's pretty tricky. I put a few hours into it and gave up. But if you're clever and have been programming for a while, you can probably figure it out better than I was able to. |
Hi @Keavon , just needed a few clarifications
|
I don't understand what you've tested. Are you saying you changed KeyDown to KeyDownNoRepeat for both of your two makings you included in your comment, then attempted to use Ctrl+A? What is the outcome of that? |
When the change to path tool action is keydownnorepeat and the select all layers is keydown using ctrl+a would result in change to path tool only. |
Since it's a bit different from what's mentioned in the issue, I just wanted to reconfirm the desired working. |
It sounds like you're identifying examples of how this is broken. And yes, we know it's broken, so the goal here is to fix it. We want it to treat both as co-equals, so the existing manner in which a higher-precedence key supersedes a lower-precedence key works whether they are KeyDown or KeyDownNoRepeat or some mixture; instead of requiring they all be of the same type. |
For example, if we update
input_mapping.rs
like so:Then CtrlA will fire both the selection of all layers...
...as well as the change to the Path tool, since one gets matched on
KeyDown
and another onKeyDownNoRepeat
. If both wereKeyDown
orKeyDownNoRepeat
, only one would match. But currently, both are matching, and we only want one to match.After implementing this fix, the following mappings should be changed from
KeyDown
toKeyDownNoRepeat
:Mappings to change
The text was updated successfully, but these errors were encountered: