I will also add to this discussion that the latest devices which run CIQ 5.* require one of the more recent SDKs for apps to build properly. This is a general rule - there may be some specific cases where you can get away with using an older compiler…
On devices that support it I would guess it is
1. at least slightly more efficient
2. uses less code (though ironically this is less important on devices that do support add)
However if you do want to support older devices as well, then you'll need to…
Usually you don't copy-paste .iq files to the GARMIN/Apps/ folder but rather the .prg files only.
To create a .prg binary use "Monkey C: Build Current Project" (instead of "Monkey C: Export project") and select the appropriate device.…
Also, I think you want to keep the original data around, so you will always apply the algorithm to the original data. (At least keep as much of it as possible. Maybe at some point if you run into a memory limit, you can cut the data set in half or something…
My app uses WatchUi.Menu. When the user clicks a menu item on "old" watches (~2 years ago), the menu is popped, and I didn't call popView in my MenuInputDelegate so far. I'm trying to port the app to new devices, and for some looks like it does…
I guess Garmin actually does tell us what colours to use, at least for devices which support the personality library [*].
[*] This seems to be every device which has CIQ 3.4 and higher.
That's not so bad, as it includes several devices which aren't getting…
I solved similar "graphic problem" two weeks ago - I wanted to design an analog watchface similar to Garmin factory default at Fenix 5 Plus but with some added features. After a huge analysis of watchface screencopies I concluded that the Garmin factory…