Re: showing window causes EXC_BAD_ACCESS
Re: showing window causes EXC_BAD_ACCESS
- Subject: Re: showing window causes EXC_BAD_ACCESS
- From: Uli Kusterer <email@hidden>
- Date: Sat, 27 Sep 2008 20:39:07 +0200
On 27.09.2008, at 19:06, Daniel Child wrote:
No. But I'm still wondering. How would you set up a reference again
if you chose to have the window released on close...without
reloading the entire nib, which is probably counterproductive.
Well, for some windows, you might not need another reference.
Imagine you have a window of which you can open several, like the "Get
Info" panel in some apps. Your window controller would listen for the
window closed notification and commit suicide upon receiving it, and
the window would go away. Though I agree that it's a better design to
just not use this flag, and just have the window controller destroy
itself when the window is closed, and take down the window the regular
way.
Also, there are cases where someone else is going to retain a window
anyway. Closing a window will simply call -release, if someone else
retained it, the object won't go away.
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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