04-10-2019 04:38 - edited 04-10-2019 06:06
04-10-2019 04:38 - edited 04-10-2019 06:06
I'm working on a clock face and one of the important features is to disable display.autoOff behavior. On a Versa watch for testing, with a setting to toggle autoOff, display.autoOff=false doesn't keep the display on as expected. Testing in the simulator it appears that display.autoOff is always true even immediately after being assigned false. Is this an issue with the simulator, my code, or something else?
Code:
import { display } from "display";
....
display.autoOff = false;
display.on = true;
console.log("forceDisplayOn: " + data.forceDisplayOn + ", display.on: " + display.on + ", display.autoOff: " + display.autoOff );
Log:
[6:35:50 AM]forceDisplayOn: true, display.on: true, display.autoOff: true
Answered! Go to the Best Answer.
04-10-2019 13:02
04-10-2019 13:02
I found autoOff to be unreliable (admittedly a year or so ago). I found that I had to detect display.onchange and turn the display back on.
04-10-2019 13:02
04-10-2019 13:02
I found autoOff to be unreliable (admittedly a year or so ago). I found that I had to detect display.onchange and turn the display back on.
04-11-2019 11:44
04-11-2019 11:44
I can wish the API worked as described but knowing it doesn't is just as helpful! Thanks!