Re: Mysterious crash with NSTableView
Re: Mysterious crash with NSTableView
- Subject: Re: Mysterious crash with NSTableView
- From: Andreas Falkenhahn <email@hidden>
- Date: Mon, 29 Aug 2016 15:39:16 +0200
On 29.08.2016 at 02:10 Kyle Sluder wrote:
> Delegates are different because they are often messaged in response to
> various exogenous events. Some of these events might happen transiently
> during window teardown, which is usually a time of massive fluctuation
> in an app’s object graph. This is why -windowDidClose: is a good time to
> nil out delegate properties that point back and the window controller
> which ultimately owns the control.
So does this mean that this is potentially dangerous?
[NSApp runModalForWindow:win];
[tableView setDelegate:nil];
[tableView setDataSource:nil];
[win release];
Should I move the "set to nil" calls to -windowDidClose instead?
--
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