richard@gryphon.CTS.COM (Richard Sexton) (07/06/88)
I may have found a bug. Maybe everyone knows about this and it's an old
bug, but I thought I'd describe it here anyway.
The programs being used: Arthur Johnson's ``Showfont'' and ``The Calligrapher''
from Interactive Softworks.
_Showfont_ is a program which simply displays all characters in a specified
font.
_The Calligrapher_ is a comercial font editing program.
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.
I'm not sure where the bug lives, but I got around it by taking
out the ``addbuffers'' in my startup-sequence.
My system is very stock, other than running Matt's/Steves's shell.
Thank you and good night.
--
If you were to flatten out Wales, it would be bigger than England.
richard@gryphon.CTS.COM {backbone}!gryphon!richardpapa@pollux.usc.edu (Marco Papa) (07/06/88)
In article <4754@gryphon.CTS.COM| richard@gryphon.CTS.COM (Richard Sexton) writes: |I may have found a bug. Maybe everyone knows about this and it's an old |bug, but I thought I'd describe it here anyway. |The programs being used: Arthur Johnson's ``Showfont'' and ``The Calligrapher'' |from Interactive Softworks. |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. What probably happens is the following. Show font runs, shows you the font, and when it exits the font is left in memory (Note: a bug in the 1.1 software would crash a machine if a program was doing an EXPUNGE). Then you run calligrapher, which picks up the "old" font in memory, then it allows you edit it, and SAVING it to disk. From the description it look like that Calligrapher does not Expunges the old font and substitutes to it the new one. When you exit calligrapher, then the "old" font is still in memory, and therefore gets displayed by another run of showfont. If this is the case, I would consider it a bug in calligrapher. One easy way to check is to write a "small" program that does an AllocMem of 16Meg or any number larger than available memory). The call will fail but will have the beneficial effect of automatically expunging devices, libraries and FONTS currently unused. Then run show font. If Calligrapher saves the font in the font: directory then this time the new one should be picked up. If it stores it in its own drawer, you are out of luck. You'll have to copy it to the appropriate directory. -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
cmcmanis%pepper@Sun.COM (Chuck McManis) (07/07/88)
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.