Complete
over 4 years ago

Screen refresh

I have build a Watch face (GVWatch) that can only update on screen what has been changed. This can reduce battery power even more because drawing is reduced to a minimum. In the sumilator it works perfect but when I test it on my own device the first second it looks okay but then only the parts that are changes are visible. It would be nice if the simulator would work the same and even better: the watch screen is not cleared before the Watchface OnUpdate() is called so the watch only updates what is changed :) 

Is there a general reason for this last behavior or could this be something that could work?

Gerard
Parents
  • over 4 years ago in reply to jim_m_58

    I didn't read any forum. Bought my Garmin a few months ago and out of frustration that most WF used a lot of battery or lacked options I started my own a few weeks ago. I am a professional developer for more than 20 years so I probably do not know ... I did optimize code and use onPartialUpdate(). 

    My vision is the less code you run, the less computing power you use, the less battery it consumes. As large portions of the display do not change at all why keep executing code to update it? I understand that you have been assigned a different vision so it makes no sense to go into this further.

Comment
  • over 4 years ago in reply to jim_m_58

    I didn't read any forum. Bought my Garmin a few months ago and out of frustration that most WF used a lot of battery or lacked options I started my own a few weeks ago. I am a professional developer for more than 20 years so I probably do not know ... I did optimize code and use onPartialUpdate(). 

    My vision is the less code you run, the less computing power you use, the less battery it consumes. As large portions of the display do not change at all why keep executing code to update it? I understand that you have been assigned a different vision so it makes no sense to go into this further.

Children