It's exact experiences like this that make me scratch my head and say "who is testing this" and "how can it be allowed to ship with clearly broken functionality in the foundation frameworks"?
Products with faults like this can not be allowed to ship, especially from a company such as Apple. Problems like this are the exact problems that are found if the functionality is properly tested on the supported devices just once. Again, how and why are people letting the product ship with billed functionality that is clearly non functional? Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Matt Neuburg <m...@tidbits.com> Sender: cocoa-dev-bounces+zav=mac.com@lists.apple.comDate: Fri, 09 Nov 2012 15:48:15 To: David Duncan<david.dun...@apple.com> Cc: <cocoa-dev@lists.apple.com> Subject: Re: iOS 6 built-in view controller save-and-restore disappointing On Nov 9, 2012, at 1:54 PM, David Duncan wrote: > On Nov 9, 2012, at 1:45 PM, Matt Neuburg <m...@tidbits.com> wrote: > >> >> On Nov 9, 2012, at 1:29 PM, David Duncan wrote: >> >>> On Nov 9, 2012, at 11:30 AM, Matt Neuburg <m...@tidbits.com> wrote: >>> >>>> It turns out that the new iOS 6 UIViewController/UIView state restoration >>>> does not work through a restart of the device! >>> >>> How was the device restarted? >> >> I turned it off and then I turned it on. > > Well, some people have "restarted" the device by holding home+lock until it > rebooted, which is basically a force-reboot and at which point all bets are > off. > >> Why - are you suggesting it *is* supposed to work through a restart??? m. > > > Yes it is. Well, it doesn't for *any* app that I've written that uses the new automatic save-and-restore - and I've written half a dozen, as test cases. They all work, in the sense that I can test in the normal way: e.g., run from Xcode, click the Home button (on the device or Simulator), stop in Xcode, and run from Xcode again - presto, we launch with restore (proven by how it looks, by logging, etc.). But if we put the application on a device, launch it from the device, click Home, restart the device, and then launch from the device again, there is no state restoration: we are doing a cold start. Do you actually *experience* the contrary? If so, is there some piece of the puzzle needed here in my code that would make the difference between save-and-restore working *most* of the time and save-and-restore working even after the device is restarted? m. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com This email sent to z...@mac.com _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
