Chris Speciale

> If you are currently maintaining memory without using 'HXCPP_GC-MOVING', it is recommended to release the old memory through `System.gc()` before generating new memory. > > Like this: SceneA loaded...

This is normal behavior due to the shape cache. Increased memory usage is the tradeoff for vastly improved cpu performance on large volumes of text. The cache should only keep...

After considering this some more, I think it might make sense to only use the cache after a certain number of word breaks to avoid adverse affects of using text...

Yea, I didn't consider the implications of a large number counter. The shape cache allows us to quickly append or change text without having to calculate the positions of the...

The problem is actually due to the way TextEngine internals work. Essentially, we should only be caching individual glyphs which is both memory efficient and cpu efficient, but OpenFL instead...

Currently, if you use JUSTIFY alignment it will not use the cache at all. I thought I would point that out.

> > The problem is actually due to the way TextEngine internals work. Essentially, we should only be caching individual glyphs which is both memory efficient and cpu efficient, but...

> > Currently, if you use JUSTIFY alignment it will not use the cache at all. I thought I would point that out. > > what does justify do other...

A workaround for now could be to use multiple text fields inside a single container. TextField(Score:) TextFieldWithJustify(120000) TextField(| Combo:) TextFieldWithJustify(3000) TextField(| Accuracy:) TextFieldWithJustify(100%) Now, due to the nature of justify...

Justify simply doesnt use the cache because it breaks and is rarely used for long dynamic text. I just pushed a change allowing you to turn off the cache entirely...