-
Notifications
You must be signed in to change notification settings - Fork 169
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
'Turn off monitors on workstation lock' quirk #57
Comments
There's not much one could do... at least nothing straight forward. Your problem is, that the session isn't locked while the screensaver is running.. you wouldn't be able to see it otherwise... (since the lock screen is protected and usually not accessible by other apps) Well... we could further delay the monitor turn-off and see if the user had been idle the entire time... Like delaying by 3 seconds and the user being idle for at least 2.4 |
I should clarify that I meant the logon screen exclusively, not the Win10 "lock" screen. I have the lock screen disabled, so I go directly to the logon screen when waking up from the screensaver (old Windows behavior before Microsoft thought up the awful lock screen). It's not really too big a deal, I just figured I'd mention the behavior in case there were a solution for it. Thanks! |
…s user idle (#57) this fixes issues with screensaver activated locks and allows us to turn off the monitor again after it's been turned on by mouse movement (eg. by accident; had been requested before on DonationCoder's) In theory, T-Clock can now react on any kind if "lock" whether it's a "lock" or "switch user" that caused the logon screen to trigger. Though Windows doesn't yet allow us to turn off monitors or detect if the system is idle when it wasn't a "lock" that caused it
does this release work for you? |
Yes, the 5 second delay makes a big difference, thank you! Now when the screensaver is active, and the mouse is moved, instead of immediately turning off the monitor(s) it waits 5 seconds, allowing you to log in without having to shake the mouse again to wake the monitors up. Perfect, much appreciated fix! |
Win10 Pro x64 Build 1607 14393.82
T-Clock Redux x64 - 2.4.1 Build 419
The 'Turn off monitors on workstation lock' feature works great, however I have found one quirk with it:
When the screensaver is active, bringing the PC back to life with a mouse movement/key press stops the screensaver and brings up the logon/lock screen. It appears that T-Clock is interpreting this as the PC being locked (which it already was), and is turning off the monitors. An additional mouse movement/key press is then required to turn the monitors back on.
I don't know if there's a way for T-Clock to distinguish between a user-initiated lock (ALT+CTRL+DEL then ENTER) vs the state of the screensaver changing from active to inactive then going to the logon/lock screen, but it seems that it's treating both events the same and is turning off the monitors when you're actually trying to unlock the PC.
Any thoughts are appreciated, thanks!
The text was updated successfully, but these errors were encountered: