View Single Post
  #23 (permalink)  
Old 01-29-2007, 09:27 AM
schettj's Avatar
schettj
morsus mihi
Offline
Location: Not from around these parts
 
Join Date: Oct 2006
Posts: 3,017
Reputation: 3616
schettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIP
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
640K of program memory is an awful lot.
The default setting uses 32kb
People often use 64kb - I am currently running at 256kb (262144) which seems to be a reasonable tradeoff.

A little poking around with google shows that this setting is used by the os to cache fonts as they are rendered:

http://msdn2.microsoft.com/en-us/library/ms900737.aspx
Quote:
The value specified for the limit is the size in bytes of the glyph cache per realized font. This number is automatically multiplied by 4 for antialiased fonts.

A realized font is any unique combination of font, height, weight, and effects (for example, outline or emboss). A font is realized the first time an application uses it for drawing, and is unrealized when the application deletes the HFONT.
Note that's per-font! So setting this very high can eat a lot of memory when running PIE, with multiple fonts.

So, going crazy with this setting may not be a good idea
Reply With Quote