Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!newstop!sun!cmcmanis
From: cmcmanis@sun.Eng.Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Multiple assigns and stuff.
Message-ID: <124443@sun.Eng.Sun.COM>
Date: 11 Sep 89 19:03:59 GMT
References: <19465@gryphon.COM> <13842@super.ORG> <4466@cps3xx.UUCP> <16253@watdragon.waterloo.edu>
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 55

In article <16253@watdragon.waterloo.edu> (Richard Czegledi) writes:
>Is there any way to fool the system into letting you do multiple
>assigns to multiple directories.
>Instead of using paths.

Yes, Bill Hawes and Rico Marriani(sp?) have both independently developed
programs that let you do this. Bill's is available on the latest Wshell
disk (it's a commercial product I believe) and Rico's was posted to the
source groups so you should be able to get it from kilowatt or on a Fish
disk. Note that there are serious problems when it comes to the policies
for "writing" into such a psuedo directory. Further you can get directory
listings with multiple identical files and that confuses the heck out of
some programs which (quite reasonably) make the assumption that the name
space of the file system is unique.

>
>Also, I'm having a whopper of a bad time with the program SetFont.
>I like running in interlace, and I use my own 16 point font (same size
>as topaz, but smoother).

Not too suprising because the system doesn't really support the ability
to hijack the default font out from underneath it and that is what SetFont
does. However, it is unarguably useful and your problems are related to
probably an old version of SetFont.


>  Anyway, I find I also have to "Expunge"
>libraries every now and then or I start to loose my mind.  When I
>expunge, or start to run low on memory, then my pretty font dies.

What happens of course is that your font gets expunged from memory
like everything else with a zero open count and yet your windows are
still using it. Think about what it means to have your font memory on
the free pool, can you imagine some of the effects that would occur
from such a situation ? SetFont 2.0 is the latest I believe and it
leaves the font open in memory (and thus unexpungable).

> But ever since I've moved to 1.3, the window
>title bar stays the same height of topaz 8, but whenever I activate the
>window, the name of the window is rendered in the new font (so it sticks
>it's ugly head into the window).

Sounds like an old version of setfont as well.

>My startup sequence is approx. as follows:
>Setfont Pons

This should probably be "Setfont Pons WINDOW" (or whatever the syntax is
for just changing the window fonts) because you can crash the system if you
use a large font and some menus get rendered with it. 

-- 
--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.