Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!sunic!chalmers!mathrt0.math.chalmers.se!news
From: d6caps@dtek.chalmers.se
Newsgroups: comp.sys.mac.programmer
Subject: Problem with MacApp ".Clone"
Message-ID: <1990Feb26.185646.21302@mathrt0.math.chalmers.se>
Date: 26 Feb 90 18:56:46 GMT
Sender: news@mathrt0.math.chalmers.se (Evald Nyhetsson)
Reply-To: d6caps@dtek.chalmers.se (Per Bergland)
Organization: Chalmers Univ. of Technology, Gothenburg, Sweden
Lines: 39

From: d6caps@dtek.chalmers.se
Newsgroups: comp.sys.mac.programmers
Subject: Problem with MacApp ".Clone"
Expires: 
References: 
Sender: 
Reply-To: d6caps@dtek.chalmers.se (Per Bergland)
Followup-To: 
Distribution: world
Organization: Chalmers Univ. of Technology, Gothenburg, Sweden
Keywords: MacApp 


I'm using MacApp 2.0b9.

Question :
   What's the meaning of making a method if you don't use it?

I intended to use the Tobject.Clone method and relied on Apple having
made multiple instances where necessary (i.e. where fields are objects
or handles).  It turned out this wasn't so. Why not?

Problem examples:

1)  Cloning a TView doesn't clone the subviews.

2)  is what made me discover this.  I cloned TCluster and got the
    same text in both after changing one. Freeing also gave some
    serious errors. It seemed the fDataHandle wasn't duplicated.


So, what?

Am I supposed to change all MacApp-classes and create the Clone method
myself? (Mucho work :-( )


Per Bergland  
d6caps@dtek.chalmers.se