The layout system is designed so it's not necessary for your to try to determine what device the app is running on. While there isn't currently a way to designate a layout for a class of devices (e.g. all square screens or all round screens), you can…
Use the C preprocessor so you can include/exclude code on a line-by-line basis 
(I don't claim this is a good practice from a maintainability or readability standpoint, or from any pov other than being able to maximize memory savings by compiling the least…
Short answer: not realistically—at least not without Arccos’ (and probably Garmin’s) help.
Why:
Right so now we're back to the original topic: comparing each of our two algorithms.
To answer your question, I already explained what I expect to see in the other topic, but I'll try again:
- viewing the zones as "touching" (some would say "overlapping…
It is true if your app is installed on a specific device, but not, when a user that has this type of device is trying to install it, because then it depends on their FW version, so instead of being able to install it they might get a warning…
Is the FW on your f7s up to date? Sounds like a bug there, as this works fine for me on other devices.
I don't think it's a bug, Fenix 7 series users have been complaining about this behaviour for a few years. At least it's not the kind…
