I’m looking at one of the samples in Cloub
1 Like
What size are you trying to use? There’s a limit to how large the glyphs can be but as long as you remain in that range it should work. You can also use Pebble FCTX instead if you need dynamically sized fonts. The package is called pebble-fctx, you can install it by running pebble package install pebble-fctx
1 Like
Correct me if I’m wrong, but I think this is a broader-scope question.
If a TTF font is uploaded, why does the size of the font need to be specified at compile time. Why can’t it be used at any arbitrary size, and rendered at any size at run time?
To answer this, and correct me if I’m wrong about this too, it’s that the TTF fonts are “baked” during build, resulting in a bitmap-esq lookup for rendering the font. This is also why it is encouraged to select the characters needed using regex, like [0-9:APM ] to only create bitmaps for characters 0123456789:APM[space] to tell the time.
1 Like
That sounds like about what I’m seeing. Looking in manifest.json in the example I was following I discovered the ttf font referenced in two entrees, one for each of the font sizes referenced in main.js. I have to change the size value in both places or I get an error.
It is a bit like when I changed a color and got an error. I discovered I had to declare the RGB values for that color name. I was used to HTML/CSS where there are default color names understood by whatever renders them.
Got where I wanted to go for my first attempt and managed to publish and then publish a minor version changed.
1 Like