[CIQBUG] Location.toGeoString() text cannot be displayed on 920XT

The string data returned by Location.toGeoString() contains the degrees symbol, which appears to cause problems when rendering text in the simulator for the 920XT for each of the fonts in FONT_XTINY, FONT_TINY, FONT_SMALL, FONT_MEDIUM, FONT_LARGE, FONT_NUMBER_MILD.

I realize that there are issues with entering non-ascii characters into Eclipse, but this issue is different in that it seems to work for some fonts on this device and all of the fonts on the other devices. I'm fairly certain that this issue affects applications that are run on the 920 as well.

tonny.madsen over 10 years ago

I use a degrees symbol in my Distance to Start data field: "°"

Not sure if it is the same degrees symbol of cause.
I haven't had any reports of problems on 920XT or fenix3

travis.vitek over 10 years ago

I've uploaded a test case that displays the result of Location.toGeoString() using each of the available formats and each of the available fonts. Feel free to test it out yourself. It can be downloaded from here.

tonny.madsen over 10 years ago

I've uploaded a test case that displays the result of Location.toGeoString() using each of the available formats and each of the available fonts. Feel free to test it out yourself. It can be downloaded from here.

I have downloaded and run your example and it does look a bit strange.
I have uploaded a small swf movie, so you can see for yourself.
Please I run under MacOSX.

Brandon.ConnectIQ over 10 years ago

Thanks for the great, little test app, Travis. I see a few different issues here that I'll report based on how the app behaves in the simulator. There's some inconsistency in how the number fonts treat some of the characters, too, which I don't really understand. I could understand if a number font did not support certain characters, but all of the number fonts should behave the same way.

tonny.madsen over 10 years ago

Thanks for the great, little test app, Travis. I see a few different issues here that I'll report based on how the app behaves in the simulator. There's some inconsistency in how the number fonts treat some of the characters, too, which I don't really understand. I could understand if a number font did not support certain characters, but all of the number fonts should behave the same way.

One thing is spaces on vivoactive, which have a square around them... But not so on any other devices.

Brandon.ConnectIQ over 10 years ago

Yeah, I saw that. I'm not sure whether to treat that as a bug, since that's more an issue of the character missing from the font. I'll add it to the ticket, just in case.

Former Member over 10 years ago

I believe the only characters guaranteed to be included in the number fonts are 0-9, '.', ':', and '-'.

We will investigate including additional characters (e.g. space) as a part of the ticket Brandon created.

jim_m_58 over 10 years ago

Brian, how about a comma, as that's often used when displaying large numbers?

Former Member over 10 years ago

I think there are a number of additional characters that an argument could be made for in number fonts. We will try to look at them all.