Ticket Created
over 4 years ago

VEGAS-6266

Transferred

️Missing on Fenix 5 Series

The glyph for Heart️ Unicode 'Red Heart' (U+2764) is missing on the Fenix 5 series of watches but present on the Forerunner 645m and Vivoactive 3m.

On the Fenix 5, you see the diamond-? character instead of the expected heart.

In this particular case, the unicode character is being embedded into `strings.xml` and loaded and displayed using `Ui.loadResource`.

rconradharris
Parents
  • over 6 years ago

    Check out Appendix B of the UX guide in the SDK, as that shows what's available by device and specific font.  It's a bit dated though....  I'm surprised this is available at all, and while you mentioned the 645m, i suspect it might not be on the 645 (the memory difference with music devices, and the f5 also doesn't have the memory of music devices).

    So...  You may not want to count on it being available, and handle it yourself with a bitmap or your own custom font for things like this. (an "icon font")

Comment
  • over 6 years ago

    Check out Appendix B of the UX guide in the SDK, as that shows what's available by device and specific font.  It's a bit dated though....  I'm surprised this is available at all, and while you mentioned the 645m, i suspect it might not be on the 645 (the memory difference with music devices, and the f5 also doesn't have the memory of music devices).

    So...  You may not want to count on it being available, and handle it yourself with a bitmap or your own custom font for things like this. (an "icon font")

Children
  • over 6 years ago in reply to jim_m_58

    Thanks for the pointer Jim, yeah a bitmap fallback might be the best way forward here.

  • over 6 years ago in reply to jim_m_58

    I recently worked on a side project to generate the UX guide appendices from the data used by the simulator. If we can get this into place, the documentation will be much easier to update and will hopefully get updated more frequently than it has been (ideally every time we make an SDK it'd be re-generated).

    Unfortunately, this script generates data based on the simulator configuration and not the actual device configurations (every device team seems to do things differently), so cases where the simulator configuration doesn't match the device configuration would not get caught. As mentioned above, we've made some changes that should avoid some of these issues moving forward, but I don't think it will eliminate them.