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

Feature Request: Detect conflicting keyboard shortcuts #36016

Open
volatile-torpedo opened this issue Nov 19, 2024 · 0 comments
Open

Feature Request: Detect conflicting keyboard shortcuts #36016

volatile-torpedo opened this issue Nov 19, 2024 · 0 comments
Labels
Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams

Comments

@volatile-torpedo
Copy link

Description of the new feature / enhancement

I wish I had a screen cap of it, but if memory serves me right, the PowerToys.Run process used a little under 300MB of memory. Unfortunately, I don't have a screen shot of it. However, shortly after two distinct changes, memory usage skyrocketed.
Image

The two changes are:

  • Upgrade to Windows 11 24H2
  • Installation of OpenAI ChatGPT client from the Microsoft Store

ChatGPT was my primary suspect because I noticed that it had a conflicting default keyboard shortcut (Alt +Space). Several cleanups, reinstallations and install methods later, changing the keyboard shortcut to anything else (Alt + Shift + Space) did the trick.

So, just like some screen capture apps that, on startup, inform you that another process hooked into the PrtScn key, it would be nice if PowerToys would be able to detect for that condition and display a courtesy warning to the user.

Scenario when this would be used?

This feature can be useful at startup, but also any time while it's running. Apps are constantly competing for keyboard shortcuts, but it's often unclear which one will take precedence.

Supporting information

No response

@volatile-torpedo volatile-torpedo added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams
Projects
None yet
Development

No branches or pull requests

1 participant