Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!mit-eddie!bu-cs!purdue!decwrl!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Did I find a bug ?
Summary: No, it's a feature.
Keywords: Fonts
Message-ID: <59047@sun.uucp>
Date: 6 Jul 88 19:07:42 GMT
References: <4754@gryphon.CTS.COM>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 18

In article <4754@gryphon.CTS.COM> (Richard Sexton) writes:
->Basically the problem occurs when you do this: Display a font by using
->_Showfont_. Exit. Edit the font with _The Calligrapher_. Save it to
->disk. Click to back and display it with _Showfont_.
->
->What you will see now, is the OLD font, the one you had on disk
->previous to saving the font you just editied.

This is the way it works, the font hangs out in memory until the very last
second even after it has been closed. No checking of the fontfile datestamp
is used to determine if a newer font is available. After editing and saving
the font use flushlibs from the debug menu to clear the old font out of 
memory and then run showfont again. 


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.