Unexpected, certainly; is it a bug in the simulator?

So... if I had a watchface with this:

   function onUpdate(dc) {
    	Toybox.System.println("ON FULL");
    }
    function onPartialUpdate( dc ) {
    	Toybox.System.println("ON PARTIAL");
	}

And my console output was:

ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
ON FULL
ON PARTIAL
(etc.)

Is that a bug?

I thought the idea was that onUpdate happened every minute and onPartial every second?

Top Replies

All Replies

+1 jim_m_58 over 5 years ago

onUpdate() will happen every second if you are not in low power mode. You can see what mode you are in based on onEnterSleep() and onExitSleep()

+1 jim_m_58 over 5 years ago in reply to jim_m_58

On real devices, the switch occurs based on a gesture, the WF drops out of low power mode for about 10 seconds and then goes back to low power.

Unless you restart the sim, it can get a bit confused and the check box for low power may be wrong, in which case, just toggle it a couple of times. It's a known bug and was reported a while back.

0 9635560 over 5 years ago in reply to jim_m_58

Thanks, you also answered what would have been my next question!

0 jim_m_58 over 5 years ago in reply to 9635560

This is something you'll not notice on a device with the HW for 1hz and a watchfaces that does 1hz, unless you exceed the power budget, in which case, calls to onPartialUpdate() stop. (and may be something you want to handle with a Ui.WatchFaceDelegate.

Devices today with the HW for 1hz are the f5 like devices and newer except the fr45/swim2 (they are CIQ 1) and the venu. The venu is a bit tricky if you want to handle "always on" as you are limited to how many pixels can be on at one time and how long any given pixel can be on.