Re: Dismissing Open dlog before doc actually opens
Re: Dismissing Open dlog before doc actually opens
- Subject: Re: Dismissing Open dlog before doc actually opens
- From: Steve Mills <email@hidden>
- Date: Wed, 14 Aug 2013 13:44:49 -0500
On Aug 14, 2013, at 13:11:31, Quincey Morris <email@hidden> wrote:
> Actually, it's going to be the Window Server that removes the window from the screen. However, it may be that ordering-out an app window triggers a run loop source or event, which in turn notifies the Window Server. If so, the 'sleep' approach isn't going to work.
I only used sleep in that example to illustrate that orderOut was not hiding the window, and that there were not "deeper issues" in our code base.
> My guess, in Steve's scenario, is that a later part of the document-opening sequence is blocking the main thread for a while, but the interaction with the Window Server isn't fully finished yet, so that it gets "snagged" by the later blockage, even though the app has gone way beyond its own Open-dialog-handling code.
The document loading code loads a complex document structure, which naturally blocks the main thread.
--
Steve Mills
office: 952-818-3871
home: 952-401-6255
cell: 612-803-6157
_______________________________________________
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