Powertoy suggestion: Idle user tracker #89
Labels
Idea-New PowerToy
Suggestion for a PowerToy
Needs-Author-Feedback
The original author of the issue/PR needs to come back and respond to something
Status-No recent activity
no activity in the past 5 days when follow up's are needed
Comments
|
You can, thanks to GPO, send a logoff command instead of a screensaver. |
ryanbodrug-microsoft
pushed a commit
to ryanbodrug-microsoft/PowerToys
that referenced
this issue
Apr 14, 2020
…sult Addalthomeforfirstresult
ryanbodrug-microsoft
pushed a commit
to ryanbodrug-microsoft/PowerToys
that referenced
this issue
Apr 14, 2020
Removed additional README instructions before moving to the powerToys public branch
|
Log off or lock? I don't know if we'd do a log off as doesn't seem 'power user' and lock already has this ability. /needinfo |
ghost
added
Needs-Author-Feedback
|
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
ironyman
pushed a commit
to ironyman/PowerToys
that referenced
this issue
Feb 17, 2025
Tested with the `command-line` tag, because there's no extensions in winget until microsoft/winget-pkgs#216685 merges Also adds a link to search in the Store, though I think that won't be as useful. Lastly - also actually fixes the tag search 😅 Builds on microsoft#356 Closes microsoft#89 Probably needs microsoft#370 to feel right
ironyman
pushed a commit
to ironyman/PowerToys
that referenced
this issue
Feb 17, 2025
Closes microsoft#370 The DevHome code was great for "I need something that can lookup extensions and enumerate all of them". However, the DevHome code is a very blunt hammer when it comes to extensions. The only thing it tracks is "packages changed", and if it gets one of those, it just blows away all the extensions and rebuilds them. Yikes. This PR changes `ExtensionService` to be a scalpel. We'll keep `_installedExtensions` fresh. When we get a package install, we'll add only that package's extension to our cache, and let the `TopLevelCommandManager` know. Similarly for updates and uninstalls. That way, we can exactly change the top-level list as needed, rather than bluntly forcing all the extensions to reload. In the middle of all this, I fixed a bug where uninstalling an extension, then reloading would just fail to load extensions. This is because the old code would clear out the **whole** list of extensions when _one_ was uninstalled. That created a race where we'd be parsing the new list of all the extensions (from the reload), get an uninstall event, clear the list, then InvalidOperation as the list of extensions was modified during enumeration. There's a bunch more locking in here. This might drive-by microsoft#324 but hard to be sure. Related to microsoft#89
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today there is no good and simple way to configure logout of user after a certain amount of idle time, in for example a virtualized zero/thin client environment like vmware horizon. you have the GPO for idle rdp sessions, thats all. it would be helpful with a idle time tracker that could easily be configured to log out someone after a certain amount of time.
The text was updated successfully, but these errors were encountered: