Re: Is MKMapView just kinda messy?
Re: Is MKMapView just kinda messy?
- Subject: Re: Is MKMapView just kinda messy?
- From: Kyle Sluder <email@hidden>
- Date: Sat, 19 Nov 2011 13:28:20 -0800
On Sat, Nov 19, 2011 at 12:39 PM, G S <email@hidden> wrote:
> Unfortunately that's not in the documentation for MKMapView's
> "delegate" property, but at least it's in the doc for the protocol.
It's standard practice with delegates, as specified in the Memory
Management Programming Guide:
"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."
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MemoryMgmt/Articles/mmPractical.html#//apple_ref/doc/uid/TP40004447-1000810
--Kyle Sluder
_______________________________________________
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