-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Shortcut remap not working sometimes along with key remap #14380
Comments
I'm experiencing the same issue and it's been going on since I installed PowerToys several versions ago. Since, no update has made this better and as @zeyugao is saying, remap won't work until restart. Exact same issue with Alt + Tab remapped to Ctrl + Tab specifically, other shortcuts don't seem as affected (or affected at all). It also happens pretty randomly even when the computer isn't going to sleep. |
Still an issue with 0.51.1 |
can you verify if this is still an issue with v0.73.0 /needinfo |
Sorry for that, it's been a while since I switched to mac so I can not check it. Can @benlc check it? |
On Linux now, sorry! |
Got it. I'll close this for now then. |
Microsoft PowerToys version
0.49.1
Running as admin
Area(s) with issue?
Keyboard Manager
Steps to reproduce
I use the above settings.
It can always work, but sometimes the shortcut remap not working suddenly, even not work if I restart the PowerToys. But after restart the system, it will work again.
I will explain what is "working"
✔️ Expected Behavior
I exchange ctrl and alt, but I want to keep alt+tab to switch applications.
If it is working, this ctrl and alt is exchanged and alt+tab is used to switch applications
❌ Actual Behavior
But when not working, ctrl and alt is exchanged but alt+tab is used to switch tab in applications like chrome. I need to use ctrl+tab to switch applications. I seems that the shortcut remap is unused.
Here is the report after restarting PowerToys. But it is not working.
PowerToysReport_2021-11-11-19-39-04.zip
Other Software
No response
The text was updated successfully, but these errors were encountered: