🚀 go-pugleaf

In article <1992Oct8.172144.373@cubetech.com> andrew@cubetech.com writes:
>In article <1992Oct5.232108.994@rrz.de> fl1ger@rrz.de (Ralf  Weber) writes:
>>Why did you use buildafmdir? If I incorporate new fonts into my system  
>>I simply start up any application that uses the FontPanel, then there  
>>comes a message that the system had found new fonts, and after a few  
>>moments (depends on the amount of fonts, I guess you have to wait a few  
>>minutes for 300) the panel goes away and you can use the new fonts.
>
>'cmon, you must be pulling our legs.  I am absolutely convinced that
>this feature simply does not exist.  I have **never** ever seen this
>happen or even met or spoke with someone who has seen it happen.  I
>_always_ have to run buildafmdir - no matter how many times I run apps
>with the FontPanel, reboot, etc...
>
>
>andrew
>-- 
>andrew@cubetech.com     | "We shall not cease from exploration
>Andrew Loewenstern      |  And the end of our exploring
>Cube Technologies, Inc. |  Will be to arrive where we started
>                        |  And know the place for the first time." -T.S. Eliot

	The feature exists, but it only works for a user's private Font
list. Add a font to ~/Library/Fonts, launch an application and order front
the Font Panel.  You should see an alert panel pop-up stating that new
fonts are being incorporated into the system (or something like that) and
eventually the Font Panel will show.  This does not happen for fonts
added to /LocalLibrary/Fonts OR /NextLibrary/Fonts (not even if you're super-
user, I believe).  For those, you must buildafmdir ...

--Felix

BTW,	In 3.0, the system scans for new fonts whenever the Font Panel is
ordered front;  In 2.x, this was only done the FIRST time the panel is
brought in.  This also happens when an application uses certain Font methods,
but I don't have a list handy (check TFM).