Fonts for FR965

Actually, not that uncommon, especially for other high res AMOLD displays.  The fonts are actually set by the FW group, and not CIQ.  The other thing you'll see is the amount of white space above and below the digits can vary.  Here's the 965 (the lines show this).

Here's the f5

(no white space at all)

and even there the difference between FONT_LARGE(37) and FONT_NUMBER_MILD (52) is seen

and TINY and XTINY are the same height, but TINY is bold.

For the EPIX2, FONT_NUMBER_MILD is 88. and FONT_LARGE is 59

For the 965. FONT_NUMBER_MILD is103 and FONT_LARGE,71

(as seen by dc.getFontHeight())

If you consider that the EPIX2 is 416x416 and the 965 is 454x454, they are relative. The 265 is also 416x416 while the 265s is 360x360.  

The sim can be a bit deceptive as the image you see will be larger for the 965 than the EPIX2

Using custom fonts is an option, but that will impact your apps memory.  Custom fonts are also slower. For things other than watch faces, I stick to native fonts and do a few things in my code to adjust.

Fonts have been a source of complaints since CIQ started.  The FONT_SYSTEM_* fonts were to help the situation, but it never really happened.

So lets hope for real device and what i see on sim is only a bug related to 965 ... so far it is really bad for us developers. 

It's really not that much different than any new CIQ device introduced in the last 8 years.  Fonts have always been a royal pain when porting.

FR965 (Upper is NUMBER_MILD, lower is FONT_LARGE). For NUMBER_MILD nearly impossible to have e.g. two %3.1f values in one line. Directly compared, FR265 is the same.

FR265s ... even worse (seems to be my statement about FR265(s) is better was totally wrong)

EPIX2 (like I would expect, smallest NUMBER font small enough to have two %3.1f values in one line ... even 3 would be possible.

Venu2 (comarable to Epix2. Even FONT_LARGE is high as NUMBER_MILD and lil condensed)

So everyone can see now, what the trueth. By the way, with NUMBER_FONT you can print letters on Sim FRx65(s) ... a bug in my perspective (and hopefully also the NUMBER_FONT definition).

And Epix2 / Venu2 and FR965 are of comparable size ... no argument about readibility.

My opinion is clear: Really bad work done Garmin for us developers. I already introduced own custom fonts for FRx65(s) ... seeing this feature ... I've doubts if it is a good idea to wait for the FR965 or order FR265, who knows what surprizes are coming if the first users are getting the device ... sorry, bugs can happen, but this seems to be wanted by Garmin.

Yes, absolute true. Some of my apps need a major revamp, now. Garmin keeps their 3rd party devs busy. I'd rather like to build some new stuff.

About a year after I started CIQ and there were more than 4 CIQ devices, I decided re-write parts of some of my early apps to better handle all the new devices.

In most cases, like the 965, if they require any changes, they are trivial.  If custom fonts are used, it may mean crating news ones, as was the case with the 454x454 display on the 965

The most complex changes I've need to make in the last couple years were for the Instinct2/2s/crossover, but that's things like the subScreen and the analog hands.

It's hard to say how to make your apps more "new device friendly" as you may not do things the way I do.  It's something you'll need to learn over time.