I decided to make quite complicated watch face and at the beginning I wanted to check how my functions will be called by the WatchFace class. My surprise was quite big.
1. WatchFace has been started and my Epix LIES on the table. Function onShow is called periodically each time with new instance of my 'myView' !!! Each time my application was killed and restarted!
2. I not always call 'View.onUpdate()' in my onUpdate function because i must update only digits of seconds. Unfortunately some times my view is destroyed and I see Garmin's digital watch face! This happens every time after Ui.requestUpdate() and in other unknown to me (quite random) cases.
My layout is complicated and I call 'View.onUpdate(dc)' only once at the beginning and then only some parts of view are updated. Extortion refreshing the entire screen each time leads to significant battery drain.
Please Garmin, do not touch my view. If you must just call onHide before and then onShow. This will give as weeks more battery life. In my opinion constantly showing seconds without redrawing entire screen will use less energy then today's complicated watch face.
Thank you for reading this.
Peter.
3. Very cool would be to have a function in the View class: View.CallOnUpdateAfter(seconds) or unlocked Timer. This will not drain battery, battery is depleted as a result of malfunction View or WatchFace class (or both).
Thank you for reading this,
Peter.
I moved this thread one level up.