On Thu, Nov 20, 2008 at 12:36 PM, Keith Blount <[EMAIL PROTECTED]> wrote: > Thanks for your reply, Ken. I did search the archives (and other places to) > but didn't see the recent discussion you mentioned, so I must have missed it. > The window controller method isn't a great solution for me, unfortunately - I > tried it but it causes all sorts of responder issues given how deep my own > view controllers are already embedded into my app. The main thing is knowing > that this is all handle automatically by NSWindowController, NSViewController > and NSDocument, though - knowing that gives me the way forward, as it tells > me that I haven't got anything horrible going on but that I just need to > unbind certain table columns manually. As I only use my custom view > controller in a few places, it shouldn't be too onerous to hard code this for > now.
Consider creating an NSObjectController instance in you nib, bind your table columns to that, create an outlet from your files owner to that object controller, and then programmatically set and unset the content object for that object controller. This allows you to break the retain cycle with a single operation instead of dealing with multiple bindings, etc. -Shawn _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
