nanogui: Scalable font support ...


Previous by date: 21 Mar 2000 13:58:14 -0000 Stupid Idea (& I'm not dead yet), Darran D. Rimron
Next by date: 21 Mar 2000 13:58:14 -0000 Re: New Microwindows font support, Greg Haerr
Previous in thread: 21 Mar 2000 13:58:14 -0000 Re: Scalable font support ..., vidar.hokstad.com
Next in thread:

Subject: Re: Scalable font support ...
From: "Greg Haerr" ####@####.####
Date: 21 Mar 2000 13:58:14 -0000
Message-Id: <007201bf933b$e24528c0$15320cd0@gregh>

If you for instance load a font with T1lib, and then draw with
: more than one size, there will be lots of cached data for *every* size you've
: rendered glyphs in. This can be "fixed" by turning caching off (very bad for
: performance), or by deleting the font size information at certain points

What's the T1lib call to disable caching?  What about for deleting
all size info?


. I looked briefly into
: creating a patch for it that allocated pools of 8KB, and returned pointers to
: blocks within that pool for each allocation, and that speeded things up a lot,
: and helped memory use tremendously (the allocations in question only happen
: when a font is loaded, and the free()'s only happen when it's unloaded), but I
: never got around to cleaning up those patches... I'd be happy to give pointers
: if someone wish to have a go at it, though.

Any more info you can give me would be great.  I quickly toured the T1lib
source, but haven't had time to really get into it; too many other things on my
plate ;-)

Regards,

Greg




Previous by date: 21 Mar 2000 13:58:14 -0000 Stupid Idea (& I'm not dead yet), Darran D. Rimron
Next by date: 21 Mar 2000 13:58:14 -0000 Re: New Microwindows font support, Greg Haerr
Previous in thread: 21 Mar 2000 13:58:14 -0000 Re: Scalable font support ..., vidar.hokstad.com
Next in thread:


Powered by ezmlm-browse 0.20.