I use getVectorFont and drawScaledBitmap to draw my watchface. From the document, these two functions are supported from 4.2.1. And From the watch's version on simulator, it's 4.2.2. Which means it should support them. But it turns out not supporting them as I add if( Dc has :getVectorFont ) test in my code.
My question is why 255 with 4.2.2 can not support these functions? How can we predict the compatiblitily?
The supported devices references in the docs for getVectorFont, VectorFont and drawScaledBitmap don't list 255/255s. While these lists are often incomplete (especially long after the initial rollout of a feature), this time it looks like the omission of 255/255s isn't a mistake.
https://developer.garmin.com/connect-iq/api-docs/Toybox/Graphics/VectorFont.html
As for why? I'd guess either a hardware limitation or a marketing decision. I *think* 255 has a GPU like the devices which do support vector fonts, but maybe it has limitations they don't? Or maybe there's other limitations in the platform?
