Gorm breaking actions/outlets to instances when reparsing header files?

[Leigh Smith]

Attempting to load a class header file after adding a method to an  
instance in Gorm (CVS) produces a warning that this will break  
actions/outlets to/from instances. This seems to be a major problem  
to use when developing, since we can expect to add methods in the  
source after the initial creation and then reparse the header to  
produce new actions or outlets. In Interface Builder those actions/ 
outlets which are not modified are retained. Breaking all the actions  
and outlets can be extremely time consuming if working with a big GUI  
or Controller class.

Are there plans to improve the reparsing (loading) of class header  
files to retain existing object connections?
--
Leigh M. Smith
address@hidden
http://www.leighsmith.com