Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!udel!new
From: new@udel.EDU
Newsgroups: comp.sys.amiga.tech
Subject: Re: Want multiple default directories
Message-ID: <24969@louie.udel.EDU>
Date: 29 Sep 89 18:29:20 GMT
References: <624@tardis.Tymnet.COM> <4741@cps3xx.UUCP> <24791@louie.udel.EDU> <271@uwm.edu>
Sender: usenet@udel.EDU
Reply-To: new@udel.EDU ()
Organization: University of Delaware
Lines: 25

In article <271@uwm.edu> trantow@csd4.csd.uwm.edu (Jerry J Trantow) writes:
>Darren, although this doesn't directly address your needs, I manage to side
>step quite a few problems with a little utility called ToolChange that I wrote.

Actually, I was just offering a relatively simple solution to the problem.
Earlier in the thread many people proposed all kinds of bizzarre hacks
to WorkBench et al to "fix" the default tools, like "tool paths" and
soft links and so on.  It seemed that my solution was much easier to 
implement quickly than patches to workbench.  Thanks anyway. Maybe
you could send this to comp.sources.amiga as an example.

>Another item I have added to my programs in general is that whenever I 
>write out a project Icon I optionally send out the entire path name to the
>default tool of the project.  This ensures that if I change the path or even
>the name of the program, the default tool will reflect this change.

Maybe you should send this portion of your programs also as an example to
comp.source.amiga.  I think this would help many would-be 
brain-dead programs.  I always disliked programs that clobber the icon
when it isn't needed; especially ones that put the WRONG default tool
into a newly created icon!  Didn't CSA publish a list of "how to set
up the default tool and when to change it"?  It seemed to make much
sense when I read it.
				    A Loyal CLI Programmer
				    -- Darren