Find out if current device supports partial updates

Hi guys,

at the moment I am working on a watchface that also supports partial updates to update seconds. Is there any way I can find out if the current device is supporting partial updates? I have not found any information that is exposed via System, Application or WatchFace object, but maybe I missed something?

Use case: depending on whether seconds can be updated every second or not I want to change the position of the shown time string. I have used "onEnterSleep" and "onExitSleep" to set a flag and then paint accordingly. Problem is that also on devices supporting partial updates those methods get called and the watch face thinks it should not paint seconds. Is there a way to get around this?

Thanks!

Bye

jim_m_58 over 9 years ago

See https://forums.garmin.com/developer/connect-iq/f/discussion/5156/1hz-watch-faces---q-a

In the first post is a .zip of a very simple watchface project that does 1hz on watches that support it, and not on watches that don't. The entire thread contains other 1hz tips. (do's and don'ts)

Talkabout over 9 years ago

See https://forums.garmin.com/showthread.php?376929-1hz-Watch-Faces-Q-amp-A

In the first post is a .zip of a very simple watchface project that does 1hz on watches that support it, and not on watches that don't. The entire thread contains other 1hz tips. (do's and don'ts)

I have read this thread already but have not taken a look into the code.

do1hz = ( Toybox.WatchUi.WatchFace has :onPartialUpdate );

very nice idea :)

Thanks!

Bye

jim_m_58 over 9 years ago

That's why there was sample code.. :) Look at how do1hz is used throughout the code, including the delegate. Also there are things in both the .mc files, and comments about where you should do other things, including now to force it to exceed the power budget, so you can see what happens then.

Talkabout over 9 years ago

That's why there was sample code.. :) Look at how do1hz is used throughout the code, including the delegate. Also not there are things in both the .mc files, and comments about where you should do other things, including now to force it to exceed the power budget, so you can see what happens then.

Ok, went through the code, some points were new to me but in general I understood the concept.

I also tried to make my method exceed the execution time limit, and here it would be great to have the possibility to print the average execution time to not have to wait several minutes to figure out if the code is "too slow". I tried to measure the execution time via "System.getTimer()" but the problem here is, that the maximum average execution time for the method is 0.5ms, which I cannot measure via the system timer, as it only gives me milliseconds.

Thanks!

Bye

Shent-Aurkhan (SHN) over 7 years ago in reply to jim_m_58

Hye, the link is broken and I found one but without the attachment.

jim_m_58 over 7 years ago in reply to Shent-Aurkhan (SHN)

I updated the link to the thread in the post before yours and updated the attachment.

Here's that attachment:

4571.VS1hz-old.zip

Shent-Aurkhan (SHN) over 7 years ago in reply to jim_m_58

Many thanks