On Fri, May 23, 2008 at 1:27 PM, Shawn Erickson <[EMAIL PROTECTED]> wrote: > On Fri, May 23, 2008 at 11:49 AM, Johnny Lundy <[EMAIL PROTECTED]> wrote:
>> I can follow making a generic NSObject set to my custom class, but why >> File's Owner? > > You do this so Interface Builder knows what class the owner of the nib > will be so it can expose the correct outlets and actions when you > attempt to make connections to/from the file's owner proxy object with > other objects in the nib. To be a little clearer the above is only at play when you are editing with your nib using Interface Builder. The class you specific in Interface Builder for the file's owner isn't a factor at runtime. >> That's all well and good, but what exactly is this thing? > > It is a proxy object that allows objects instantiated in the nib to be > connected with an object outside of the nib, in this case the object > that has been specified as the owner of the nib when it was loaded. Again this aspect is only a factor at runtime. The file's owner that you see when editing a nib file is simply a graphical representation of the object that will own the nib when the nib is loaded by your application. It provides a way to make connections to objects in the nib using control dragging and like. -Shawn _______________________________________________ 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]
