Re: Is applicationDidReceiveMemoryWarning obsolete now?
Re: Is applicationDidReceiveMemoryWarning obsolete now?
- Subject: Re: Is applicationDidReceiveMemoryWarning obsolete now?
- From: David Duncan <email@hidden>
- Date: Sun, 25 Dec 2016 10:59:43 -0500
> On Dec 23, 2016, at 10:07 AM, Andreas Falkenhahn <email@hidden> wrote:
>
> Apple's docs on applicationDidReceiveMemoryWarning say that
>
> It is strongly recommended that you implement this method. If your app
> does not release enough memory during low-memory conditions, the system
> may terminate it outright.
>
> However, when creating a new "Single View Application" for iOS, Xcode 8.2 doesn't
> create a stub for applicationDidReceiveMemoryWarning. It only creates stubs
> for other delegate methods like applicationDidBecomeActive and so on.
>
> An old app of mine which I created with Xcode 3.2 still has the applicationDidReceiveMemoryWarning
> stub, though, but Xcode 8.2. doesn't seem to create it any more. Is this done
> on purpose? But why do the docs stress the importance of implementing this
> delegate method then?
Memory warnings are best handled locally, and in that respect there is both the app wide notification and the view controller method for handling them. You can certainly implement the method if you like, and if it works with your app’s logic.
>
> --
> Best regards,
> Andreas Falkenhahn mailto:email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
--
David Duncan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden