Quick Accent interferes with games

[The-Pfaffinator]

Description of the new feature / enhancement

It would be nice to have a shortcut key to enable or disable Quick Accent, because the combination of letter keys with arrows and/or Space is extremely common in games. I am aware that specific apps can be excluded from activating QA, but there are instances in games where the player would want to type, such as in chat fields or console commands. It would also be nice if the feature could activate automatically based on whether a text field is actively selected.

Scenario when this would be used?

In games that require letter button presses for movement, but also include a chat or text boxes for gameplay.

Supporting information

For example, WASD keys control movement, and Space and arrow keys control other game functions. If the movement keys are being held while the player presses other keys to jump or shoot, Quick Accent opens instead. This means Quick Accent either has to manually be disabled while playing a game, or set an app to be excluded so it does not interfere. However, it would still be desirable to use Quick Accent while typing in text boxes while gaming. One solution would be to only allow Quick Accent to activate while typing in a text box/field. Another would be to have the activation key be something that would not normally be pressed frequently in combination with a letter while in a game, such as one of the F keys. Yet another would be to have a Windows Key combination to quickly enable/disable this function on demand, instead of having to open up Power Toys menu and toggle the switch.

[Nikolas-VIII]

Adding a setting to disable the tool for Fullscreen applications might be the easiest solution.
Just like the existing option for PowerToys Run.

[wolfmic]

It is possible to add a process list to ignore, it is not optimal but it works.
I would add that this issue is probably a duplicate of #20349

[crutkas]

/dup #20349

[microsoft-github-policy-service]

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!