Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!AppleLink.apple.com!Greg
From: Greg@AppleLink.apple.com (Greg Marriott)
Newsgroups: comp.sys.mac.system
Subject: Re: ResEdit 2.1 (A question to)
Message-ID: <11526@goofy.Apple.COM>
Date: 14 Dec 90 12:01:10 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 22
References:<6698@drutx.ATT.COM> <1990Dec2.173058.28944@santra.uucp> <787@grumpy.sarnoff.com> <11502@goofy.Apple.COM> <1990Dec13.200714.43586@vaxb.acs.unt.edu>

In article <1990Dec13.200714.43586@vaxb.acs.unt.edu> 
mouse@vaxb.acs.unt.edu (Dhanapong Saengrussamee-University of North Texas) 
writes:
> Yes, I got my 2.1 off from AppleLink.  Do I still need "ResEditFixer"
> init that patch/cure some anomally of 2.0b2 or that had been "fixed"
> in 2.1?

You do not need ResEditFixer with ResEdit 2.1.

ResEditFixer wasn't made to fix anything specific to 2.0b2.  The same 
problem exists with all previous versions of ResEdit.  The basic problem 
is that when you open a non-running system file, the toolbox starts using 
defProcs and other resources from that file instead of the running system. 
 This wasn't a major problem in the past, but with System 7, support was 
added for extra stuff like system menus and color.  Compressed resources 
also cause problems because 6.0 system don't know how to decompress them.

But ResEdit 2.1 addresses all these issues.  It's great!

Greg Marriott
Just Some Guy
Apple Computer, Inc.