Closed Thor77 closed 8 years ago
Logged In: YES user_id=114903 Originator: NO
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. (By highno)
Logged In: YES user_id=114903 Originator: NO
Hi,
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]!
Bye Lars (By highno)
Hi,...
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.
best regards
Stefan