On Thu, Jul 17, 2008 at 5:42 PM, Trygve Inda <[EMAIL PROTECTED]> wrote:
> I'll have one instance of this class for each > screen, one of which will be handling the "main" screen. > [...] > Can a single class have an IBOutlet that goes two different (though > functionally identical) places? It's a single class, but there are multiple instances, each with its own storage for that IBOutlet, so each can point to different things. Why not have a TabAController class with all the functionality for handling tab A, and subclass it to make a TabsABCDController class adding the functionality for the other tabs? Then just instantiate the former three times and the latter once. It's difficult to say whether you should instantiate the TabAController class in AuxScreen.nib or instantiate it programmatically and have it be the File's Owner without knowing how these tabs' functionality will have to interrelate. Hamish _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
