If you are using dc calls and not layouts, you actually don't need to all View.onUpdate() at all. If you are mixing a lawout with dc calls, you need to do the View.onUpdate() before you do dc calls. View.onUpdate() clears the screen so any dc calls…
If you are using dc calls and not layouts, you actually don't need to all View.onUpdate() at all. If you are mixing a lawout with dc calls, you need to do the View.onUpdate() before you do dc calls. View.onUpdate() clears the screen so any dc calls…
Thanks. I think the response could be more helpful. Making "expected behaviour" known and understood outside of Garmin is part of good documentation. The API docs for View.onUpdate() should contain full details of the behaviour and the expectations…
Btw: the crash problem for downloading Birdseye sat imagery is back
I'm aware of that, but tapping that and holding it is even harder than the menu navigation. Most of the time I end up tapping something else, tapping and holding nothing at all, adjusting the screen brightness, etc. After a couple of failed attempts I…
I had this issue the first time I plugged my forerunner 55 into a new PC to charge it. It fixed automatically when I downloaded Garmin Express on the PC and added my watch
Moderator: 3021221, removed double post
Here is another report about the differences. See the posts by Travis (one of the Garmin people)
Clearing the screen is the easy part!
The part that I need some guidance on is how to work around the lack of ability to do an incremental update, because the graphics take literally seconds to draw. It seems like there isn’t a good universal way to do…
There are other reports of this where Travis.ConnectIQ has explained that trying to update only parts of a screen in onUpdate() is inconsistent, when you mix in things like alerts shown on the watch too as well as different app types.
To be consistent…
Thanks for the reply.
I'm not sure how it can be "not a bug". The simulator should simulate the watches correctly and it doesn't. The behaviour of the watches themselves is undocumented and inconsistent: either all watches should preserve…
This is well known and has been reported before and isn't a bug. When onUpdate() is called, you want to redraw everything and not just some things. The only time you can safely update only parts of the screen is in watch faces with onPartialUpdate…
