Re: Confused by memory issue with UIDatePicker
Re: Confused by memory issue with UIDatePicker
- Subject: Re: Confused by memory issue with UIDatePicker
- From: Kyle Sluder <email@hidden>
- Date: Sun, 16 Jun 2013 18:16:21 -0700
On Jun 16, 2013, at 6:08 PM, Quincey Morris <email@hidden> wrote:
> On Jun 16, 2013, at 17:29 , Kyle Sluder <email@hidden> wrote:
>
>> For this reason, that document recommends you use a weak declared
>> property for outlets to non-top-level objects. You should probably
>> follow that recommendation.
>
>
> Under the circumstances, since this is a manual RR app, just releasing the UIDatePicker [ivar] in dealloc might be a superior approach.
Meh. As a Mac programmer, your approach would indeed be my instinct, but I'm trying to train myself to be more modern. Then there's the question of whether -dealloc is appropriate, or if the view should be released sooner (to avoid a retain cycle).
What's the story with memory warnings nowadays? UIViewController never jettisons your views anymore, right? Is doing it yourself no longer recommended?
--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