• Replies 5 replies
  • Subscribers 19 subscribers
  • Views 1003 views
  • Users 0 members are here
Options
Related

SimpleDataField has very small font with non-numeric characters

djhawley
On some devices (FR235 and FR735XT) including a non numeric character such as a '-' for padding or an '@' will make the font very small and unusable.

My paceband apps (https://apps.garmin.com/en-US/apps/a18bb975-f59c-43e0-9293-a0e69061a0d8, https://apps.garmin.com/en-US/apps/cf5d8304-f4c5-4bdc-83d8-135c26a9d728)
Tell you your split at an interval, so I use non numeric characters to seperate displaying the mile number from the time at the split

It seems to happen on real devices only

Steps to reproduce
1. create simpledatafield
2. return "@" from compute
3. run on real device

expected result : normal size text to match other fields
actual result: very small text that can't be seen while running
  • the @ character is probably not available in the number font and because of that uses the text font, maybe you can use a - (dash) instead?
  • the @ character is probably not available in the number font and because of that uses the text font, maybe you can use a - (dash) instead?


    Thanks Peter, from what I saw in other threads I think you're right that in some watches it seems it doesn't have the @ in certain sizes of the font (on some devices). So I did initually use a "-" but they have the same problem I had to resort to using a "." instead
  • There is an appendix in the UX Guide that show what characters are supported in the various number fonts on different devices.
    (Appendix B)
  • Well with a . it'll certainly be a valid number...

    But I wonder whether the " - " approach is not working due to the space characters that you're using, did you try the dash without spaces approach?
  • There is an appendix in the UX Guide that show what characters are supported in the various number fonts on different devices.
    (Appendix B)


    Thanks, I had checked out the appendix, but the 235, 735XT etc is the only section without an explicity list of characters in the number font. All other devices do suggest that "-" should be in the fonts though.

    I would have thought in a simple data field it would be reasonable to include text such as miles/km but I guess they would cause the error too

    I haven't actually used spaces, my format is always just 1-2-2 etc peterdedecker I try to keep the string as short as possible so the text renders as large as possible