Skip to content
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

Quick Accent - Activation with a different key #21018

Closed
pietrocavallin opened this issue Oct 4, 2022 · 2 comments
Closed

Quick Accent - Activation with a different key #21018

pietrocavallin opened this issue Oct 4, 2022 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@pietrocavallin
Copy link

Description of the new feature / enhancement

First of all thank you very much for this fantastic tool. It really makes life easier.

However, especially as a gamer, I find myself telling you that the activation of Quick Accent while playing is not rare. The combination A or E (when using WASD) + spacebar or right/left arrow is very common.

How about adding a third button, or giving the user the option to choose it himself?

Thanks for your attention and keep up the good work!

Scenario when this would be used?

When using Quick Accent

Supporting information

No response

@pietrocavallin pietrocavallin added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 4, 2022
@crutkas
Copy link
Member

crutkas commented May 18, 2023

/dup #20408

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants