• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
MemoryWarning and loadView
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MemoryWarning and loadView

  • Subject: MemoryWarning and loadView
  • From: Bleicher Eiko <email@hidden>
  • Date: Mon, 24 Jan 2011 17:52:20 +0100
Hi,

I want to get a deeper understanding of the memory warning handling on iOS in UIViewControllers.

It seems that the default implementation of didReceiveMemoryWarning will set the view to nil, and viewDidUnload gets called. *But* this is only done when the controller implements loadView. Even if this method does nothing at all except calling [super loadView].

What is the reasoning behind making this behavior dependent on the existence of loadView? Also wondering how this is checked, as "respondsToSelector" might not be enough because the superclass implements it anyway?

Thanks,
Eiko

_______________________________________________

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
  • Follow-Ups:
    • Re: MemoryWarning and loadView
      • From: David Duncan <email@hidden>
  • Prev by Date: Creating a mouse event & event number
  • Next by Date: RE: how to change NSButton color
  • Previous by thread: Re: Creating a mouse event & event number
  • Next by thread: Re: MemoryWarning and loadView
  • Index(es):
    • Date
    • Thread