Non Anti-aliased fonts?

How is using the system fonts adding to the app's memory usage?

A bitmap with a full palette when I only need 14 colors so that I can use colorDepth=>4 is what is adding to memory usage. Specifying a palette breaks anti-aliasing. The system fonts are anti-aliased fonts so they can't be used, and I don't see an available font that can be used. If there is a font which can be used in a bitmap with a palette, how do I use it?

I see. My gut tells me that the solution you will find will:

1. be more comlicated

2. have problems with different locales

3. will eventually use more memory because you'll need to use a custom font

So IMHO the best is to keep it as is (using bitmap with full palette). Also the difference between 4bit and 6 bit is not that huge (you don't need 24bit pictures since most devices have 64 colors only)

Actually, per the memory usage dialog a 14 color (4-bit) palette uses half the memory of the system palette. I don't have any issues with my Fenix 7x where memory is concerned for this WF, but I'm trying to figure out what other devices I could support without a lot of rework. <rant> It's already bad enough that there are multiple kinda compatible kinda not API's to contend with. Having to check what I can do against monkeyVersion and have different branches doesn't make it easier to reduce the code size. Using the lowest common denominator doesn't go very far.</rant>

I don't know the answer, and I'm not sure there is an answer. When the old watches were created there probably were no antialiased fonts used, and for newer watches there is an antialiesed font, This doesn't necessarily mean that on the newer watches the old, non-antialiased fonts can also be found