On Apr 28, 2012, at 10:17 AM, Richard Somers <rsomers...@awinets.com> wrote:
> I have a number of controls with custom bindings that are programmatically > added to a view hierarchy in a window. Calling –unbind: on these controls > when the window is closes is a challenge. Why? Someone has to have called -bind::: on them. Make that thing call -unbind: when your window delegate (most likely your NSWindowController subclass) gets -windowWillClose:. > > But it actually does not seem to matter. If –unbind: is never called and the > window is closed there are no memory leaks reported in Instruments. You're probably leaking observers and might crash at some point. You said "custom bindings"; how are your bindings implemented? > > Apple has an undocumented class NSAutounbinder which apparently addresses a > problem with retain cycles when binding to File's Owner from a nib file. > However I am binding programmatically not inside a nib file. But perhaps > NSAutounbinder is somehow working in my behalf. Doubtful. I believe NSAutounbinder is only used by the nib loading machinery. > > Is unbinding my programmatic bindings when the window closes something that I > should worry about? Yes. --Kyle Sluder _______________________________________________ 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
