I'm just wondering why the font heights (returned from getFontHeight, getFontAscent etc) for the system number fonts on more recent watches are so extreme compared to the actual rendered graphics of the number digits. Compare these simulator screen shots of some tests that I did for the Fenix 5+, Vivoactive 4 and Fenix 6:

My guess would be that the ascent & descent being returned are for the original full ASCII fonts, and are not the values that match just the number digits.
I was going to use the font height values to help decide when the numbers would need redrawing (from their screen area). I guess a simple solution for my case would be to limit the ascent to a reasonable maximum value, and always set the descent to 0.
