GPSrChive Discussion Forum

Hello All,

Does anyone see any difference in how waypoint names are displayed with the 700 series?
I just noticed one of my waypoints has a white outline around it's name, I find things with this outlining very hard to read in moving situations.
It wasn't present in the older 700 I returned to Garmin and I never used this replacement 700 until after I updated it's firmware to version 8.20 so not sure if it was introduced with that or not, gawd I hope not , that would be a step backwards.

It's the exact same waypoint .gpx file used each time, all waypoints have 'City Small' set as the icon.


The old 700 beside the 276CX with no outline around the waypoint name:

Posted as GPSrChive > Montana 7x0 > Common Issues > Bug 62.

This bug also affects other Garmin models, including the GPSMAP 66 series, Oregon 7x0 series, and Rino 75x series devices.


How To Reproduce

All Devices:

• Setup > Map > Advanced Setup > Text Size > User Waypoints = <> None

• Setup > Appearance > Mode = Day

• Map Page user waypoint names are correctly displayed as Black text with White outline

• Setup > Appearance > Mode = Night

• Map Page user waypoint names are incorrectly displayed as Black text with White outline

Option 1:

• Setup > Map > Advanced Setup > Text Size > User Waypoints = None

• Map Page user waypoint names are correctly not displayed

• Setup > Map > Advanced Setup > Text Size > User Waypoints = <> None

• Map Page user waypoint names are correctly displayed as White text with Black outline

• Setup > Appearance > Mode = Day

• Map Page user waypoint names are incorrectly displayed as White text with Black outline

Option 2 (Montana 7x0 only):

• Where To? > {choose any destination} > {Do Not Select 'Go'}

• Map Page user waypoint names are now correctly displayed as White text with Black outline

I wonder if this affects the time & battery displays in the info bar at the top of the map screen in night mode, perhaps my feature request was a bug report

If I tested this correctly (I am not sure), I think, this has been fixed in firmware 9.20.