You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I almost never use Caps Lock intentionally, mostly it's accidental. Allowing PowerToys Run to use the Caps Lock button would remove the ability to accidentally turn on Caps Lock, and it would make use of a key that otherwise is not used often. It would probably be a good idea to add "Caps Lock On" and "Caps Lock Off" as possible commands in Power Toys Run, so that users could still toggle it if they really wanted.
Scenario when this would be used?
every time activating PowerToys Run
Supporting information
No response
The text was updated successfully, but these errors were encountered:
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
After tinkering a bit, I'm able to get this 99% done using the Keyboard remapping: I can remap Caps Lock, then use the new mapping as the activation shortcut. Of course I realized this right after I posted...
This is great news @mimmacci! I am glad you managed to figure this out! :)
I will be closing this issue now. Feel free to re-open if any other related issues arise :)
Description of the new feature / enhancement
I almost never use Caps Lock intentionally, mostly it's accidental. Allowing PowerToys Run to use the Caps Lock button would remove the ability to accidentally turn on Caps Lock, and it would make use of a key that otherwise is not used often. It would probably be a good idea to add "Caps Lock On" and "Caps Lock Off" as possible commands in Power Toys Run, so that users could still toggle it if they really wanted.
Scenario when this would be used?
every time activating PowerToys Run
Supporting information
No response
The text was updated successfully, but these errors were encountered: