Watch Diagnostics Display Time

I have a minimal analog watch face that I am able to get under the 30 ms average execution time. However, I am looking at the display time in the watchface diagnostics and I am surprised that it changes so much as the second hand rotates around the watch(from like 2700 to 20,000). Is there a reason for this?

Top Replies

peterdedecker over 6 years ago +2

The watch face consumes the most when the clip region contains many rows, so when your second points at the 9 (few rows) it will consume way less then when it points at the 12 (many rows)

All Replies

peterdedecker over 6 years ago

The watch face consumes the most when the clip region contains many rows, so when your second points at the 9 (few rows) it will consume way less then when it points at the 12 (many rows)

Travis.ConnectIQ over 6 years ago in reply to peterdedecker

Just to be clear, it isn't just the size and orientation of the clip region that matters. The clip region is only considered when drawing a bitmap.

The display time is based on the amount of execution time spent running virtual machine code. Every function that is used to draw to the Graphics.Dc will have an additional impact on the display time, and calls to WatchUi.loadResource() will have a huge impact on it.