> On Aug 23, 2013, at 7:35, Uli Kusterer <witness.of.teacht...@gmx.net> wrote: >> Though I still think it’s safer to NOT rely on this order, and instead >> perform the initialization in a lazy-loading accessor, so that it is >> guaranteed the first one who needs the information (and requests it using >> the accessor) causes it to be loaded, no matter what spot the code is moved >> to.
After accepting the fact that no specific sequence of method invocations can be expected, and letting this digest over the weekend, a possible nuance suddenly occurred to me: does this essentially mean that in addition to either invocation order being possible, that it is possible that the handleGetURLEvent method might be called during the applicationDidFinishLaunching method is executing, i.e. after applicationDidFinishLaunching has been started but before it completes? That possibility is the ugliest of them all -- this would mean that not only does the app not know the manner in which it was launched when it is launching, but that initial launch behavior might not even complete before that info shows up, which would suggest that proper implementation would require the handleGetURLEvent affecting only a state change, which is polled by the app, rather than handling the event when it comes in. Seems like a lot of gyrations just to launch properly, which would be solved completely just by delivering the app relevant info on how it was launched at launch time. If anyone knows whether the handleGetURLEvent could potentially be called during the applicationDidFinishLaunching execution, I'd be interested in knowing. Thanks, Brad _______________________________________________ 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
