That makes sense.
Currently what I'm doing is basically just forcing it to prerender by calling a single frame draw for each font size.
Although, this ends up being about 10 seconds, due to my using about 7 font sizes on a high resolution Android device.
That makes sense. It tends to be really slow on higher dpi screens though (naturally). Meaning on newer Android phones, it can be quite an issue.
Perhaps there's a way to use Android's native draw text and use this manual Kha version as a backup?
I haven't looked much into Kha's font drawing code yet, but I'll see if there's anything I can do when I have time.
I ran into an issue today with my screens being slow to switch.
I've tracked it down, and it seems the issue has to do with whether or not I use fonts on the screen.
I've observed this issue on Html5, but it's especially visible on Android.
I've created and example: kha-font-example
When the app opens up, tapping the screen with switch to ScreenB (which draws a font); this switch takes a relatively long amount of time.
However, once I've switched to that screen, I can switch back to ScreenA then back to ScreenB and this time the switch is instant.
Removing the font drawing from the draw method completely eliminates this issue.
Seems like a very strange issue to me. Hopefully someone else is able to reproduce this.