Documentation of Font Sizes on each watch model ???

Jeff over 4 years ago

I'm trying to support a wide range of Garmin Watches with my app.

Fitting fields on the display is one of the key challenges in supporting a wide range of devices.

I've discovered some real surprises in the meaning of FONT_TXINY, FONT_TINY, FONT_SMALL, etc across models.

Is there any documentation, any summary that shows the font sizes on each of the watches that Garmin has produced ???

0 jim_m_58 over 4 years ago

See https://developer.garmin.com/connect-iq/reference-guides/devices-reference/

But understand that some fonts, mainly FONT_NUMBER_*, can have white space above and below the characters.

This is one of the fun things about multi device support - the fonts.

0 Jeff over 4 years ago in reply to jim_m_58

Thanks Jim.

I had not looked at the detailed information about each model to find the fonts described there.

I have discovered that some fonts have space above and/or below the characters, and some do not.

That is not described, so experimentation with Ascent and Descent and setClip is required to actually fit fields to the screen.

I'd say your definition of fun could use some review :-)

Thanks

0 jim_m_58 over 4 years ago in reply to Jeff

I have a little test app that displays all the fonts with a line where they stop and end, and also the result of getFontHeight(). It comes in handy when a new devices is announced. It makes it easy to see them all. Something like this is easy to put together.

Here's the text fonts on a f5+. In this case tiny and tiny are the same height, but one is bold.

0 Jeff over 4 years ago in reply to jim_m_58

Great idea Jim.

Another related question - I found that for earlier devices like the Fenix 3, the function setClip() was not supported.

Do you have any suggestions for work-arounds ?

Thanks

Jeff

0 jim_m_58 over 4 years ago in reply to Jeff

The f3 is a CIQ 1 device, and setClip came about in CIQ 2.3. Your only option is to code so you don't need it for the f3. It's not something where you can just write your own version. BufferedBitmaps are also from 2.3 so you can't use those on an f3 either.

0 Jeff over 4 years ago in reply to jim_m_58

Thanks again Jim.

I've worked around the limitation... was hoping there was some other approach but it's fine as it is.

Jeff