...indeed... kind of a cartesian product says hell(o)!...
To keep complexity limited, I can see multiple, different extensions and only the application has to load only what is needed... it could even be instance based rather than prototypical, even though latter I prefer (for encapsulation reasons and simplicity of use). For starters I will go for support of single neopixel string w/ zig-zag and not-zig-zag.
A) Is there reason not to group fontAbc and modMmmN, since they are build-time conditioned? - https://github.com/espruino/Espruino/blob/master/libs/graphics/graphics.h#L64L68 and https://github.com/espruino/Espruino/blob/master/libs/graphics/graphics.h#L70L72 , respective
B) What is STM32F4's alignment in structs? - byte for things <= byte, 2 bytes for things of 2 bytes, 4 bytes of 4 bytes
I assume SAVE_ON_FLASH flag is at runtime accessible somewhere...
© Espruino, powered by microcosm.
Report a problem