Re: Class Hierarchy in the Interface Builder
Re: Class Hierarchy in the Interface Builder
- Subject: Re: Class Hierarchy in the Interface Builder
- From: Jake McArthur <email@hidden>
- Date: Fri, 28 May 2004 11:18:15 -0500
On May 28, 2004, at 8:41 AM, email@hidden wrote:
Two Controller ControllerA and ControllerB have common Code, therefore
I introduce an AbstractController as a superclass of ControllerA and
ControllerB. The AbstractController has only be added in XCode while
the other Classes are used in the Interface Builder, too. Now if I
look at the Class Browser of the Interface Builder ControllerA and
ControllerB are still subclasses of NSObject. While the code is
working correct, the missing class in the IB might be confusing...
Any idea to fix this problem?
Try creating the abstract superclass within Interface Builder and then
putting your controllers as subclasses of that. Create files where
appropriate.
That's what I would try anyway. No idea if this is ideal.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.