Acknowledged
2 months ago

Degrees symbol in GEO_DMS string shows up as a strange character

When formatting a position in DMS format on the Instinct Crossover and Venu Square 2 like this:

var dms=posn.toGeoString(Position.GEO_DMS) as String;
The degrees symbol in the string shows up as Unicode 57520, hex 0xE0B0 instead of decimal 176.
This happens in the simulator in SDK 7.4.3.
I didn't test every device but others I tried do not have this problem.
trudelta
  • 2 months ago

    I was able to look into this both on device and in the simulator.

    I found that on device, the degree symbol was showing up on VenuSq2, but not on Instinct Crossover.
    The degree symbol was not showing up for either in the simulator, which makes me believe it is more than likely a simulator issue, and possibly with the Control and Data Processing (CDP) that the Instinct uses where the Venu does not.

    I went ahead and made a bug ticket with those findings, and sent it to our tools team to further investigate.

    The picture on the left is on the device, the left is in the simulator. 

  • 3 months ago in reply to FlowState

    It would be nice to know if the behavior is correct on the real Instinct Crossover and Venu 2 Square.  I had to add some extra code to clean up the string for these cases.

  • 3 months ago

    Thanks for the context!

    Regardless, I think it’s strange that toGeoString() returns U+E0B0 instead of U+00B0, since U+E0B0 is a private use unicode character. Is there some reason toGeoString() can’t just return U+00B0?

    U+00B0 is actually rendered correctly in the simulator for Venu Square 2, for both number and non-number fonts.

    But if it works on a real Venu Square 2 device, then I guess it’s ok. 

  • 3 months ago

    This has been the case pretty much since CIQ began, where the degree symbol from toGeoString() doesn't show correctly in the sim but it does on actual devices.  I know it was reported way back when because I reported it (this was long before the forums changed so you won't find a bug report).  One of the Garmin folks responded and I finally got to the point where for some reason it wouldn't change and just seen it as a sim fluke ever since.  This was 2015 or 2016..  It's the same on the most of the earliest devices to the most recent.  It shows correctly on the original vivoactive, but didn't with the va-hr (called "Tall Watch" before it was announced but was a preview device in the sim) for example.  Looks like it took a decade for others to notice, so probably a very, very low priority.  It shows as a empty box or a diamond with a ? depending on device.

  • 3 months ago

    (I'm also guessing that maybe it's not a coincidence that U+E0B0 is being used in place of U+B0)