Complete
over 4 years ago

WERETECH-9575

By Design

VA4 firmware 5.0 always clears the goalView dc every second

VA4 firmware 5.0 always clears the goalView dc every second.

The dc is always cleared every second during the display of the goalView.

My watch face implements a goalView but only renders the content once at the beginning and then draw over to get an animation like behaviour.

-> https://apps.garmin.com/en-US/apps/fc3f9b9f-add6-46cb-8e0b-9a2172a04c31

With the new firmware the goalView is cleared each second and draws only the new content. This leads to false rendering of my goalView and flickering of the complete VA4 display.

Please fix, thanks.

To reproduce this bug set the floors goal to the next number and go for a small climb. ;-)

Other watches are fine e.g. F5X, F6X

TheMagician
Parents
  • over 4 years ago

    > 1. The the screen gets black with each onUpdate check the first clip the arc is drawn every onUpdate but still flickers

    Yes. The vivoactive4 family devices clear the screen before calling onUpdate. This is the expected behavior. As I said above, our current stance is that applications are expected to redraw the entire screen when onUpdate is called. If you are not doing that, then we are currently considering this to be a bug in your code.

    > 2. why is the SDK behaviour on each device different? I don't want to spend my time to develop the code for each device. (the different screen sizes are already enough)

    It isn't different between each device. It is different between devices that use our old graphics framework and those that use the new framework. Most apps don't notice this difference because they update the entire screen when onUpdate is called.

Comment
  • over 4 years ago

    > 1. The the screen gets black with each onUpdate check the first clip the arc is drawn every onUpdate but still flickers

    Yes. The vivoactive4 family devices clear the screen before calling onUpdate. This is the expected behavior. As I said above, our current stance is that applications are expected to redraw the entire screen when onUpdate is called. If you are not doing that, then we are currently considering this to be a bug in your code.

    > 2. why is the SDK behaviour on each device different? I don't want to spend my time to develop the code for each device. (the different screen sizes are already enough)

    It isn't different between each device. It is different between devices that use our old graphics framework and those that use the new framework. Most apps don't notice this difference because they update the entire screen when onUpdate is called.

Children
No Data