Thanks, Kyle. This also fixed my problem with the MapView. Because MapView is so self-contained, I had it in a xib presented in a popover, and didn¹t even keep a reference to the MapView. (I do now.)
On 11/20/11 2:01 PM, "cocoa-dev-requ...@lists.apple.com" <cocoa-dev-requ...@lists.apple.com> wrote: > On Sat, Nov 19, 2011 at 2:06 PM, G S <stokest...@gmail.com> wrote: >>> >> "Examples of weak references in Cocoa include, but are not restricted to, >>> table data sources, outline view items, notification observers, and >>> miscellaneous targets and delegates. [. . .] Likewise, when a delegate >>> object is deallocated, you need to remove the delegate link by sending a >>> setDelegate: message with a nil argument to the other object." >> > >> > Noted, thanks. This seems like an oft-overlooked problem when lots of >> > controls have their delegates set in the XIB; there's no easy way to >> > look at the code and make sure that there's a delegate-clearing >> > statement for each one. > > You just need to make it a habit. When you add a delegate connection, > add the setDelegate:nil at the same time. > > Soon ARC's zeroing weak references will make this concern a thing of > the past. But for now, you need to internalize it. > > --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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
