Hi,
There has been a long-standing issue with the way that Garmin default SDK projects not only encourage, but also demonstrate, use of getObscurityFlags that is, technically, according to the documents, illegal and wrong: The whole getObscurityFlags controversy... - Connect IQ Bug Reports - Connect IQ - Garmin Forums
That was mainly just an irritation until I noticed that, in fact, the entire getObscurityFlags subsystem is fundamentally broken on at least two devices.
Therefore, please can I ask anybody who uses getObscurityFlags to help layout their data fields to please vote on this bug:
Known devices that it definitely affects are Venu and Fenix 6x but I strongly suspect there are others.
Please verify the behaviour on your device and contribute to the ticket if it affects you.
Sorry if I'm getting a bit shouty, but I have entire ranges of data fields that quite literally cannot be laid out based on dimensional information as they are dependant on knowing which side of the clock face they occupy so as to draw dials accordingly.
Thank-you,
Righteously-Shouty of Dublin