Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uakari.primate.wisc.edu!uwm.edu!csd4.csd.uwm.edu!trantow
From: trantow@csd4.csd.uwm.edu (Jerry J Trantow)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Want multiple default directories
Message-ID: <271@uwm.edu>
Date: 29 Sep 89 17:21:09 GMT
References: <624@tardis.Tymnet.COM> <4741@cps3xx.UUCP> <24791@louie.udel.EDU>
Sender: news@uwm.edu
Reply-To: trantow@csd4.csd.uwm.edu (Jerry J Trantow)
Organization: University of Wisconsin-Milwaukee
Lines: 19

In article <24791@louie.udel.EDU> new@udel.EDU () writes:
>keeps track in a separate file of where the tool for each icon gets copied
>that could at least be added to Workbench, maybe as an option.  How about a
>command that runs through all the .info files on a disk and fixes the
>default tool entry to have the right info?  That seems easy enuf.
>		  -- Darren
 
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.
ToolChange allows you to set the default tool of any icons.  It can also be 
used to add tooltypes.  When I first wrote it I thought I would be using it 
to interchange files between different programs.  (example, select all the 
files in a dpaint directory and change them to use digipaint) but instead
I find myself using it when I change the program name or the program path.

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.