Memory Usage (Font Rendering Engine)

[trogluddite]

Cheers Matti - that's good to know; I've often been tempted to use a custom font, especially for very small writing.
Seems odd that string -> ASCII should use so much memory!

[matti]

Cheers Matti - that's good to know; I've often been tempted to use a custom font, especially for very small writing.
Seems odd that string -> ASCII should use so much memory!

Yeah, well it's not the conversion itself, as i still do it but with a different primitive. More of a "bug" on the parser. Or maybe It's just not ment for being used like that. In my schematic there's way over 2000 parsers. It all adds up and devs prob thought it would be used once or twice per schematic.

Anyhow it's not really needed in the custom font rendering thing. I uploaded the fixed rendering engine that uses way less resources for all FS users to enjoy:
https://app.box.com/s/vn8avfzav4yk738holyi


edit: Changed the original topic to reflect the findings..

[trogluddite]

2000 parsers

Makes sense, the parser is probably storing partial matches, and maybe regular expression strings, inside the components. I just took a look one of my old SM projects that had a lot of parsers in it, and that's pretty greedy for memory too.