What is the order of fonts by size?

My datafield tries to use the biggest font that fits the text to be displayed to the place available. The text can include letters, so numeric-only fonts are not of interest.

Currently I only try the fonts available in CIQ 1.0.0, but users ask if I can make the fonts bigger. So I started to look into it, and would need to get the right "generic" (true for all devices) order of fonts.

I assume that both of these are true:

CIQ 1.0: FONT_XTINY <= FONT_TINY <= FONT_SMALL <= FONT_MEDIUM <= FONT_LARGE
CIQ 1.3: FONT_SYSTEM_XTINY <= FONT_SYSTEM_TINY <= FONT_SYSTEM_SMALL <= FONT_SYSTEM_MEDIUM <= FONT_SYSTEM_LARGE

But is there a way to merge these 2 lists into 1?

In general what is the difference between FONT_FOO and FONT_SYSTEM_FOO?

Top Replies

flocsy🤠 over 2 years ago in reply to FlowState +1

Tested all edge devices in the simulator, and only edgeexplore2 and edge1040 have the space in the FONT_NUMBER_*

All Replies

0 flocsy🤠 over 2 years ago in reply to FlowState

I agree, it's all matter of tradition and what you're used to. We learned in Hungary to use "," for decimal, but I would never do that today. But strange that "," is not in the font because it is used as decimal in some places but more importantly it's strange because it is even used in the US for the grouping.

Phone: I think it's easier to group but that is even more of a personal preference. I don't think there's any national or international standard on that. Probably even adding + at the beginning of international numbers is not 100% a standard, as it also works usually as 00

0 FlowState over 2 years ago in reply to flocsy🤠

flocsy🤠 said:
But strange that "," is not in the font because it is used as decimal in some places but more importantly it's strange because it is even used in the US for the grouping.

The annoyingly idealistic side of me agrees with you 100% (that's the side which is always fruitlessly complaining) but the resigned cynic says "classic Garmin".

To it's on par with not allowing mixed metric/imperial units in Connect despite over a decade of complaint, or even something as simple as not supporting a space in numerical fonts for some devices (which actually has some consequences for something like a simple data field where the font is selected automatically *)

(*) Actually, if a simple data field returns a string, IIRC on older devices the use of a numerical font would be based on whether the string is restricted to a *subset* (**) of the available characters in numerical fonts, but in later devices, I think a non-numerical font is used for any returned string, regardless of its contents. I saw the latter behavior when I installed a CIQ data field which returns a number as a string and the text was tiny, but only on newer devices. I recompiled the data field from source (it's derived from an open-source app), only changing the return value to a Number, and the text was back to the expected large size for numerical fonts.

(**) Ofc this meant that certain strings which could be displayed in a large font for a complex data field would displayed in small font for a simple data field.