Re: Is calling "-applicationOpenUntitledFile:" for app-open (but not app-reopen) out of fashion?
Re: Is calling "-applicationOpenUntitledFile:" for app-open (but not app-reopen) out of fashion?
- Subject: Re: Is calling "-applicationOpenUntitledFile:" for app-open (but not app-reopen) out of fashion?
- From: Quincey Morris <email@hidden>
- Date: Wed, 02 Mar 2016 10:25:34 -0800
- Feedback-id: 167118m:167118agrif8a:167118sTU_LM6P_D:SMTPCORP
On Mar 2, 2016, at 10:00 , Daryle Walker <email@hidden> wrote:
>
> If this is a policy change …
Yes and no.
With state restoration enabled (the default), the application re-launches to the same state as when it terminated. If there was no untitled window at quit, there’s none when it starts again.
I’d suggest you avoid trying to “fix” this by opening an untitled window. Under some circumstances, the system is free to terminate your app’s process and then to restart it later. Your fix would cause untitled windows to appear magically at random times, from the user’s point of view.
You can verify that your app is handling the app delegate message correctly by using the scheme option to run your app from Xcode without state restoration. Other than that, go with the flow, and let the system do what it wants to do with state restoration. Alternatively, you could opt out of state restoration completely.
_______________________________________________
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