• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSWindowController versus other NIB Owners
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSWindowController versus other NIB Owners


  • Subject: Re: NSWindowController versus other NIB Owners
  • From: Shawn Erickson <email@hidden>
  • Date: Thu, 15 Feb 2007 18:29:39 -0800


On Feb 15, 2007, at 6:08 PM, Julien Jalon wrote:

Well... as you said it: the nib owner must release the top-level
objects... so does NSWindowController. You can achieve the same
behavior with your own (not NSWindowControllers) nib-owners by using
-loadNibNamed:externalNameTable:withZone: and NSTopLevelObjects key...

Personally I think using -[NSNib instantiateNibWithOwner:topLevelObjects:] is easier. Why create the dictionary, etc. when you can more directly get exactly what you need. Of course it is only available on 10.3 and later.


-Shawn
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >NSWindowController versus other NIB Owners (From: Seth Willits <email@hidden>)
 >Re: NSWindowController versus other NIB Owners (From: "Julien Jalon" <email@hidden>)

  • Prev by Date: Re: NSWindowController versus other NIB Owners
  • Next by Date: How to ensure one instance running per session?
  • Previous by thread: Re: NSWindowController versus other NIB Owners
  • Next by thread: Re: NSWindowController versus other NIB Owners
  • Index(es):
    • Date
    • Thread