🚀 go-pugleaf

In article <1991Jan8.173617.12144@msuinfo.cl.msu.edu> jap@convex.cl.msu.edu (Joe Porkka) writes:
>peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
>
>>Use function OpenDiskFont() instead of OpenFont().
>>I'm too lazy to type an example here, but look into the program
>
>Also, in my experience, OpenDiskFont does NOT check to see
>if the font is already loaded, and will load a duplicate.

Hmm, I'm told this by everyone, but it doesn't fit with my
experiences:
As I already told, I'm lazy, so I used OpenDiskFont() everytime
for loading a new font. As this was in a very memory critical
demo, I watched carefully for memory consumption or even memory
loss. Nothing harmful ever happened. (Hmm, worst case scenario:
everytime when my request came in a real tight memory situation,
then all old stuff was flushed first, so perhaps there were
delays by this? It really got slow on low memory.)

Question to those with wisdom:
Could it be that OpenDiskFont() is intelligent enough to look into
RAM first, without explicitly calling OpenFont()? Or that a
duplicate font gets loaded over an already existing one in RAM?

>I WISH there was no such thing a OpenDiskFont.

Right. If not already happened, OpenDiskFont() should get 
enhanced the mentioned way, so that it can be used safely 
as the ONLY font selecting function. Or am I missing some
special feature of the pair OpenFont()/OpenDiskFont()?

-- 
Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk