On Tue, 26 Apr 2011 01:19:48 -0400, Jeffrey Walton said:
>It sure would have been helpful if viewWillDisappear was sent as
>documented. When the home button is pressed, and the home screen is
>presented, the view has clearly disappeared (no offense Alex).
Listen to what you're being told. The sig
It seems like you need to do something when the app resigns from the foreground
— if that is the case just listen for
UIApplicationDidEnterBackgroundNotification from that view controller? It
(kind of) makes things easy that way.
As the app enters background, it surely has “disappeared” but no
> It sure would have been helpful if viewWillDisappear was sent as
> documented. When the home button is pressed, and the home screen is
> presented, the view has clearly disappeared (no offense Alex).
I was seeing this when switching tabs, not when the home button was pressed.
-Heath Borders
hea
On Mon, Apr 25, 2011 at 11:04 PM, Heath Borders wrote:
> I've seen this behavior also, specifically on iOS 3.1 while using a
> UIViewController inside a UINavigationController inside a
> UITabBarController.
YES - that is nearly my setup (iOS 4.3.2). I don't have the
intermediate UINavigationContro
The view is not being hidden - the whole app is. viewWillDisappear is called
when within the life-cycle of a view, its actually about to get removed from
the visible hierarchy.
There are two life-cycles you are mixing up: app lifecycle and view controller
life cycle. The two do not mix.
On Ap
I've seen this behavior also, specifically on iOS 3.1 while using a
UIViewController inside a UINavigationController inside a
UITabBarController.
-Heath Borders
heath.bord...@gmail.com
Twitter: heathborders
http://heath-tech.blogspot.com
On Mon, Apr 25, 2011 at 9:59 PM, Jeffrey Walton wrote:
>
