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

Suggestion Box: title bar context menu entry to activate Always On Top #20788

Closed
VulcanTourist opened this issue Sep 23, 2022 · 3 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@VulcanTourist
Copy link

VulcanTourist commented Sep 23, 2022

Description of the new feature / enhancement

I never use the Always On Top feature of PowerToys, for one reason: I can never remember the hotkey required to enable it. Even if I could use the Shortcut Guide to identify it - which I cannot because it's not documented there - I also cannot remember the hotkey required to access the Shortcut Guide! Yes, I suck at recalling hotkeys and many other infrequently used details, and I've been diagnosed with a memory deficit.

For this reason, I am heavily reliant upon GUIs to do their job and self-document all the myriad things I am capable of doing. There is currently no GUI method of activating Always On Top, but that is easily rectified: add an entry to the context menu of windows' title bars to toggle Always On Top.

Scenario when this would be used?

A title bar context menu item to toggle Always On Top is "obvious" in a way that a hotkey that is not self-documenting and must be remembered to be useful is not obvious. The context menu of title bars is also the obvious place for this self-documenting GUI control, since the purpose of the title bar is to document and control the attached window.

Supporting information

Not everyone can remember a hotkey, but everyone lacking visual impairment can see a GUI menu entry.

@VulcanTourist VulcanTourist added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Sep 23, 2022
@davidegiacometti
Copy link
Collaborator

/dup #15387

@ghost
Copy link

ghost commented Sep 25, 2022

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!

@ghost ghost closed this as completed Sep 25, 2022
@ghost ghost 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 Sep 25, 2022
@VulcanTourist
Copy link
Author

Thank you, @msftbot, for finding what I did not.

This issue was closed.
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