Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!gvgpsa!gvgpvd!andyp
From: andyp@gvgpvd.GVG.TEK.COM (Andy Peterman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wish for next ResEdit
Message-ID: <1158@gvgpvd.GVG.TEK.COM>
Date: 21 Jul 89 17:03:44 GMT
References: <9175@mva.cs.liv.ac.uk>
Reply-To: andyp@gvgpvd.GVG.TEK.COM (Andy Peterman)
Organization: Grass Valley Group, Inc.; PVD
Lines: 21

In article <9175@mva.cs.liv.ac.uk> phil@mva.cs.liv.ac.uk writes:

>It would be nice if ResEdit would look in the System folder for a customisation
>file full of TMPLs etc that are specific to each user.  I use ResEdit to
>edit some custom resource types, and every time I make a change to the type,
>or get a newer version of ResEdit I have to make a copy of ResEdit, and
>use that one to modify the resources in ResEdit (not the copy) and then
>throw the copy away.  If I then intend to edit my modified resources I have
>to re-launch the newly modified ResEdit.  Couldn't it just read a file (so
>I didn't have to use it to hack itself) and then I could mess about with
>the file and not ResEdit !!??  The coding to do just that can't be THAT
>hard (can it??)

The latest release version of ResEdit (1.2) does what you ask.  It will look
at all open files for the TMPL's.  The file that you're currently editing
is searched first, and the System file would normally be the last to be
searched.  Therefore, just keep the TMPL's for each resource you're editing
within the same file and ResEdit should find them.  If you have some common
TMPL's, stick them in your System file.

	Andy