-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
[Settings] Re-phrase column headers for clarity #13710
Labels
Idea-Enhancement
New feature or request on an existing product
Product-Keyboard Shortcut Manager
Issues regarding Keyboard Shortcut Manager
Product-Settings
The standalone PowerToys Settings application
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
Comments
Agree. The whole KBM (including its settings) should get an overhaul to be more self-explainatory and easier to use. |
If ui changed, naturally #docs should follow |
1 task
/dup #10389 |
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! |
1 task
1 task
1 task
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Idea-Enhancement
New feature or request on an existing product
Product-Keyboard Shortcut Manager
Issues regarding Keyboard Shortcut Manager
Product-Settings
The standalone PowerToys Settings application
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
Seen more then one issue where somebody mixed up the column of shortcuts. When looking at it again, the left one says "shortcut" which can be interpreted as both "key press" (like keyboard input) or "output" (which = OS input). The words "mapped to" say nothing about "on which end", it could also mean "mapped to physical keys". We can solve this by using better words.
Output(still ambigous)We should also check the explaining text to be up-to-date, while at it.
I guess this is a sub-item for #2027
Originally posted by @rmcguinn in #13623 (comment)
The text was updated successfully, but these errors were encountered: