when proximity is loaded and in "pause mode", it prevents
the regular startup of my screensaver. If the device is in range, the screensaver will never switch on.
Logged In: YES
true - there is a major problem with the proximity command. It seems I was already sleeping while implementing it. It is always executed - not just when proximity is detected and even regardless of the pause state.
I will fix this today and release a new nightly build then. Thanks for [using|testing|reporting a bug]!
Fixed in SVN.
The second issue "no switch on of screensaver while device in range" is normal behaviour. If you don't like that you could set the proximity command to an ignorable command.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.