Is setClip() for epix2 serve a purpose?

Hello- I have been working on a watch face targeted to just the epix2 and have a couple of noob questions on the AMOLED programming:

1) Is there any reason to use the setClip() method within onUpdate()? It is unclear from other posts or docs on whether this does anything on this device w/o partial updates.

2) Similarly, is there a reason to worry about the amount of computations or ms per onUpdate() call wrt power consumption or otherwise?

3) For lower power/burn in testing, is there any way in the Simulator to see what % of pixels you are using? (to stay under the 10% limit)

4) On my actual watch, after the lower power/burn in switch-over, the screen will then also dim after several seconds. Is there an event to indicate when that happens? Or, is there a property that I can check that indicates the watch is in this dimmed mode?

Thanks in advance!

Top Replies

jim_m_58 over 4 years ago +1

1) I can't think of any reason. in onUpdate() you always want to draw everything to handle all the different watches.

2) You want to think about how the battery could be impacted and want to make sure…

All Replies

jim_m_58 over 4 years ago

1) I can't think of any reason. in onUpdate() you always want to draw everything to handle all the different watches.

2) You want to think about how the battery could be impacted and want to make sure you don't trip the watchdog timer.

3) In the sim, start View Screen Heat Map. You don't see the %, but if you do more than %10, it will be flagged

4) There is no way you can check for this.