> On 17 Jul 2015, at 6:20 am, Mike Abdullah <mabdul...@karelia.com> wrote: > >>> Is it trying to be clever and re-use existing accessory views, or is a >>> fresh one created each time? >> >> Why do you ask? Is this a known problem? > > My thinking is _setSuperview: seems somewhat a surprising place to crash. > > I’m hazarding a guess that the accessory view is not a fresh one, and still > has a reference to its previous superview. Apple’s code doesn’t expect that > situation, and finds the pointer to the previous superview to be invalid > perhaps. > > This is Apple’s bug, but if my guess is correct, you could probably work > around it by manually _removing_ your accessory view from NSSavePanel once > the panel returns, rather than leaving semi-attached there.
In my case the accessory view is reused, in that it’s defined in a nib and referenced by an outlet. I keep a strong reference to it so it is ‘owned’ by the controller, and added to each save panel as needed. I’m not doing anything special to clean up when I’m done with the save panel - I’ll look into whether manually removing it and/or clearing the superview reference fixes the problem. —Graham _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
