On Sep 21, 2011, at 11:59 AM, Gavin Stokes wrote: > When our app gets a notification that it's going into the background, it > clears the tableview that serves as its primary UI element. However, when > the app returns to the foreground, it still briefly contains the items that > were supposedly cleared. They remain there for a second after the app > resumes, then disappear. This creates an unpolished and jarring UI. > > My guess is that iOS stops drawing the UI as soon as the app starts whizzing > away into the background, and likewise doesn't resume drawing it immediately > after it returns. Does anyone know if that's true? I'm wondering how to > prevent this spastic-looking UI.
UIKit takes a snapshot of the view hierarchy as it was when your application goes into the background and uses that when it comes back to the foreground. It remains until your UI has had a chance to redraw itself. -- David Duncan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
