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
So, sometimes the current way that the tool works is somewhat gimmicky if you need quick keystrokes or maybe you are playing a video game, the key sequence activation might be annoying, and enabling/disabling the tool back and forth in the PowerToys settings or tray is quite inefficient.
Thus, I suggest adding a hotkey combination to Enable/Disable the tool directly with some short audio to indicate the new state, much like the "Always on Top" tool. I can take part in implementing such feature.
Scenario when this would be used?
Quick enable/disable without opening the settings, Playing video games, writing fast without the need for accents, any case of tool inconsistency.
Supporting information
No response
The content you are editing has changed. Please copy your edits and refresh the page.
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Description of the new feature / enhancement
So, sometimes the current way that the tool works is somewhat gimmicky if you need quick keystrokes or maybe you are playing a video game, the key sequence activation might be annoying, and enabling/disabling the tool back and forth in the PowerToys settings or tray is quite inefficient.
Thus, I suggest adding a hotkey combination to Enable/Disable the tool directly with some short audio to indicate the new state, much like the "Always on Top" tool. I can take part in implementing such feature.
Scenario when this would be used?
Quick enable/disable without opening the settings, Playing video games, writing fast without the need for accents, any case of tool inconsistency.
Supporting information
No response
Tasks
The text was updated successfully, but these errors were encountered: