-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Scribble working with font_add()... somehow #87
Comments
Needs checking against |
It was a nice dream while it lasted :( |
Huh. Looks like |
From some of my testing, I haven't seen glyphs cache disappear at all. I've tried flushing the texture memory. Haven't had any issues with the texture or the glyphs at all. So we could cache the results of the glyphs after drawing the entire string, fetching the font info and storing it, and then add the texture as a sprite if there's concerns of the glyph/texture possibly being cleared at random? |
jesus, this has been almost two years in the making now |
That is has been indeed |
Adding two gists to here that I've previously dabbled with when testing with making
I'm considering taking some pages from Collage and adding a mini texture page builder for the purpose of Scribble being able to store multiple font textures. And then if we get a large character set, Scribble can break the charset down into multiple fonts, extract their characters and data and add to a custom texture page. Making it easier (and more optimized for vertex/texture swaps). If we were to go down this route, I'm happy to expand upon my current gists scripts (down below) that already do showcase some of the current issues at hand, and poke in a custom texture page builder for Scribble. https://gist.github.com/tabularelf/f493624796dd8bbba85466101ad1eabd |
I've realized from this comment here that the custom texture page side of things might not be as farfetched... Shouldn't hurt then to try this out. |
Largely complete now. Thanks everyone for your help and advice. |
No description provided.
The text was updated successfully, but these errors were encountered: