OBSCURITY COMBOS - CHEAT SHEET & AMBIGUITY

Here are all the possible combinations (so far - Garmin could introduce new ones) for round and semi-round devices.

An ambiguity exists.... For example look at the "1" values in the Fenix 6 for 6 fields, for example.... You can't tell if the TOP LEFT or the BOTTOM LEFT of the field is the one that is obscured. Is this a bug in the simulator or a flaw in the obscurity logic? No way to know if you need to move over objects/text to the right more near the top or the bottom of field. Ugh.

GARMIN: implement this simple API method:

x = getLineWidth(y) where Y is the line #, X is the width at that line.

Top Replies

peterdedecker over 5 years ago +2

It would be really cool to be able to get a getFieldPosition as (combining that with width and height) would allow you to have your datafield have other behavior depending on the position it is in.

I think…

All Replies

TobiasLj over 5 years ago

DaveBrillhart said:
You can't tell if the TOP LEFT or the BOTTOM LEFT of the field is the one that is obscured.

Why can't you do that? There is a bug when calling onLayout, it's only done once and not for every field. See jim_m_58's replies in this thread: https://forums.garmin.com/developer/connect-iq/f/discussion/207952/simulator-and-datafield. But from the picture above it is obvious that for the first top left is obscured and for the second bottom left is obscured.

DaveBrillhart over 5 years ago in reply to TobiasLj

Don't you see the issue? On the top one, the TOP of the field is more obscured than the BOTTOM of the field. So if you are writing text in the top half, you need to move that text over to the right more than on the bottom of the field. You might not have a desire to do that... but I hope you see the issue - that you can't tell that the other field would require different logic.

jim_m_58 over 5 years ago in reply to DaveBrillhart

As was mentioned there's a bug in the 3.1.6 SDK with onLayout. Try going back to an earlier SDK (I forget when the bug was introduced). Put a prinln in onLayout and make sure it's getting called for very field in your current layout in the sim.

TobiasLj over 5 years ago in reply to DaveBrillhart

DaveBrillhart said:
the TOP of the field is more obscured than the BOTTOM of the field.

True since the bottom isn't obscured. Ohh, might be one pixel but since the line is in the center that is where you have 100% of the width available.

In the 8 field setup you will have fields that are obscured both top and bottom.

peterdedecker over 5 years ago

It would be really cool to be able to get a getFieldPosition as (combining that with width and height) would allow you to have your datafield have other behavior depending on the position it is in.

I think I actually filed (a few years ago) a feature request for this :)

Nikeow over 5 years ago in reply to peterdedecker

since the obscurity flags are the same eg: 7 between watches that have 4 fields vs those of the fenix 6 series,, how does one determine the difference?

eg; I can use a large font on the 4 field layouts but the same font on a fenix 6 for flag 7 would be too big for that field

DaveBrillhart over 5 years ago in reply to Nikeow

You know the height of the field... so you can pick the proper font that fits even as the field height varies between devices. Same with width. Say obscurity = 7 and height = half of width.. then you know it is a half screen field.