Re: Mysterious crash with NSTableView
Re: Mysterious crash with NSTableView
- Subject: Re: Mysterious crash with NSTableView
- From: Andreas Falkenhahn <email@hidden>
- Date: Sat, 27 Aug 2016 22:55:29 +0200
On 27.08.2016 at 18:10 Alex Zavatone wrote:
> Buuut, to the mind of the person learning this or trying to fit all
> the complexity of learning this in their head, it might be wise in
> the docs to remind the programmer that they need to do this and why
> with a, "just in case you are assuming that your code is ready to
> function now, please remember that the objects that end up making a
> working tableView require that the tableView's dataSource object
> and delegate object need to be assigned, generally to the hosting
> view controller's instance of self. If this causes you to raise an
> eyebrow in confusion, the reasons why you must do this are xxx and
> yyyy. Likewise upon deallocation of the tableView (if it gets
> called), these objects will need to be set to nil after zzzz but
> before the tableView object is able to dispose of itself."
Huh? "Remember that you have to set this property to nil before you
release the object" would already be sufficient...
By the way, I still don't know whether setting the delegate to nil
before release is a general rule or does it only apply to NSTableView?
Should I also set my button delegates to nil before the buttons are
released?
--
Best regards,
Andreas Falkenhahn mailto:email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden