feature request: Respect Locked state

[therealjohnsnow]

Hello again!

It's a fantastic app and very grateful for your hard work. I have another request for your kind consideration :)

Sometimes, when going away for lunch break, my default muscle memory is to lock the PC via Win+L key.
Normally, this locked state would allow the PC to go to sleep at per the specified Win settings, therefore minimizing any power waste.

Hoowever, when the MouseJiggler is enabled, going into Win+L locked state will prevent the PC from sleeping.
I understand this is the underlying purpose of the app (prevent sleep), but was wondering if there could be an option for the app to 'inactivate' itself when going into locked state, i.e Respect the Locked state.

This will be great for people who want Jiggler to be active during certain hours, and inactive when they put the pc in lock mode manually (i.e. don't need the pc to be active during lunch break)

Thanks!

[cerebrate]

Not a bad idea for an option. I don't know when I'll have a chance to get to another release, but I'll add it to the list.

[cyberangel]

+1

[jdrch]

@therealjohnsnow As a temporary workaround, you could have AutoHotKey kill the mousejiggler.exe process whenever Win + L is pressed.

[danangua]

Set the interval to 60s or longer works, unless you have a very bad luck.

[nnyj]

Another workaround that worked for me was disabling the lock screen via regedit:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization]
"NoLockScreen"=dword:00000001

[cyberangel]

Another workaround that worked for me was disabling the lock screen via regedit:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization] "NoLockScreen"=dword:00000001

But that wouldn't lock the computer as intended, right? What's the point?

[nnyj]

On Windows 10/11, there was an additional lock screen on top of the usual login screen. Disabling the lock screen helps to prevent the screen from staying awake. Mouse jiggler will stop jiggling at the login screen as intended.

[cyberangel]

I see, you're right. After disabling the "lock screen", it works as intended. Thanks.