Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!bloom-beacon!usc!apple!sun-barr!decwrl!shelby!polya!ali
From: ali@polya.Stanford.EDU (Ali T. Ozer)
Newsgroups: comp.sys.next
Subject: Re: copying Controls (Buttons)
Message-ID: <10906@polya.Stanford.EDU>
Date: 27 Jul 89 03:43:06 GMT
References: <23996@labrea.Stanford.EDU> <10884@polya.Stanford.EDU>
Sender: Ali T. Ozer <ali@Polya.Stanford.EDU>
Reply-To: aozer@NeXT.com (Ali Ozer)
Organization: .
Lines: 20

In article <10884@polya.Stanford.EDU> aozer@NeXT.com (Ali T. Ozer) writes:
>"copy" is supposed to make a copy of only the top level object; all 
>referenced objects are shared. There's another method, "deepCopy," I believe,
>that duplicates the whole tree of objects. 

Yet another example of Why One Shouldn't Read News Unless One Has Had
At Least One Coffee That Morning.

I'm wrong above; I just got a chance to look through the ObjC docs
in the Appendices volume of the Tech Docs, and it says that the copy
method is supposed to make a duplicate of the object, duplicating
as much of the referenced stuff as reasonable. I was confusing "copy"
with "shallowCopy." 

Given this, it does indeed seem like Button (and various other AppKit
objects) do not respond properly to the "copy" method. I'll make a
suggestion concerning this...

Ali Ozer, NeXT Developer Support
aozer@NeXT.com