microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
111.73k stars 6.58k forks source link

Always On Top QOL feature #32285

Open UnbridledNephilim opened 7 months ago

UnbridledNephilim commented 7 months ago

Description of the new feature / enhancement

Somewhere under the always on top settings, such as below the "excluded apps" area, it would help me greatly to see another box that reports all of the processes that are currently being affected by the app.

Scenario when this would be used?

I always forgot to use the hotkey to UNPIN whatever process, and then suffer tons of notifications that something is being used by Always On Top. But I can't remember what the heck to open up and UNPIN. There doesn't seem to be a way to check what needs hot-keying to stop these notifications, at the moment. If there is, someone should tell Copilot, because I've just had some very frustrating runaround-type exchanges with it, to try to find this information, and it always ends up getting to a step that says something like, "Now go to the processes tab and look for the file you suspect to be affected, and blah..." It doesn't seem to understand that if I had any suspicions whatsoever, I'd have just gone there and not to the AI for help. 🤦‍♂️ Of course, I did look to see if there was an assist available that is smarter than Co-Pilot with regards to the Always On Top feature of PowerToys, but no joy. If a help line is available I didn't see it. So I came to give this suggestion, instead.

Supporting information

I'm sure there is a way to make this info available right there on the settings page, or perhaps make the notifications reveal WHICH file you should pop up and hot-key. This sounds like a pretty fast and easy fix that would have saved me about three hours so far today, and however long it's still going to take me to find that stupid window.

UnbridledNephilim commented 7 months ago

I looked but only saw a lot of people wanting the disabling of always on top to also cut the ties to the windows it was utilizing, and that's a nice idea, but I think mine's better, because what if you want to disable those windows you don't use often, but you have a few that you want to remain persistently on top every time you open them? With a report window, you could just locate which ones need affecting and leave the rest persistent. This reporting feature might already exist in some form, and if so, this whole suggested feature should instead read: A much clearer, and prominent (within the documentation) explanation of the existing method for reporting the affected processes, including where it can be found.