> > No, then the window will be uncloseable. What needs to be different > depending on that property is whether you call -release, not whether you pass > the -close call up to super. If you're using ARC, you don't get to control > whether you call release. Therefore, you need to set releasedWhenClosed to > NO. > > If you're experiencing leaks when releasedWhenClosed is false, then that's a > separate bug in your code, which you need to fix.
No, I’m not using ARC. releasedWhenClosed is YES. I alloc/init the NSWindow subclass and store it in a retained property. When I get the Close notification, I send a Close to the window, then I set the property to nil to release it. If I don’t call [super close] this all is well and it calls dealloc ok when I set he property to nil. I’m not experiencing any leaks, this code was ported (imported in bits) from the pre ARC days (Mac OS X 10.4 I think) and I’m trying to make it work on Mac OS X 10.10. Are you saying that dealloc calls close? Since it’s being released straight after the close is sent, does this make the releasedWhenClosed setting a bit irrelevant anyway? I don’t have a problem with setting releasedWhenClosed to NO, it’s just there was a comment on the code saying that it made a LOT of difference having to set to YES and I’m just trying to figure out it’s supposed to work with releasedWhenClosed == YES. All the Best Dave _______________________________________________ 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
