Garmin Edge Data Field Size Feature

This may only apply to Garmin EDGE cycling computers. But it is a logical feature that would be very helpful to add to fix screen display issues.

When the device goes into AUTOPAUSE mode, Garmin paints a 4 or 5 pixel border around the outside of the screen.Which effectively reduces the usable size of the data fields until you start to move again. However, when you inquire about the height and width of the data field, it reports that you can use the portion of the data field that Garmin blocks off with that border.

I have a pretty cool routine that dynamically positions the label and value and adjust the font size to the data field dimensions. If Garmin would report the usable size, then my label would drop down a few pixels when this border is generated. And my font sizes might reduce by one if needed to fit horizontally in the reduced usable data field size.

Anyway, if anyone watching this forum has sway into the feature updates, consider this. Here is a screenshot of the issue, the top field's label is obscured during stop time by that border. I could work around by detecting stop and assuming the border is drawn, however, if autopause is OFF, then this border is not drawn by Garmin even when stopped, and there is no way to detect if an autopause event triggered.

community.garmin.com/.../1290988.jpg

Former Member over 7 years ago

I've created a feature request.

Thanks,
-Coleman

Travis.ConnectIQ over 7 years ago

What about when the varia radar adds the traffic display overlay or when a message overlay pops up from the bottom?

DaveBrillhart over 7 years ago

What about when the varia radar adds the traffic display overlay or when a message overlay pops up from the bottom?

Travis - I would think those are both dismissable conditions, right? A temporary overlay... you acknowledge, and dismiss. Whereas the border is non-dismissable... it persists and obscures the data field display. Just thinking out loud.

Former Member over 7 years ago

Hey,

Based on a discussion with team about the native behaviors of the device, we have decided that the overlay style is intended and we will not be implementing anything to handle it at this time. Thank you for your request.

- Coleman

DaveBrillhart over 7 years ago

Hey,

Based on a discussion with team about the native behaviors of the device, we have decided that the overlay style is intended and we will not be implementing anything to handle it at this time. Thank you for your request.

- Coleman

Brian - thinking more about this. I get that you don't want to return adjusted field sizes so a custom app can position content for visibility. I guess.

But isn't there an "obscurity" method that would be appropriate? I've only coded for rectangular fields, but there is an intrinsic way to tell if your content is visible or hidden. I see no reason why you would not use this to tell an app that its content is obscured.

Make sense?