Re: applicationShouldTerminate and asynch handling
Re: applicationShouldTerminate and asynch handling
- Subject: Re: applicationShouldTerminate and asynch handling
- From: Guy English <email@hidden>
- Date: Wed, 8 Dec 2004 11:10:37 -0500
On Wed, 8 Dec 2004 09:53:47 +0000, Christian Brunschen <email@hidden> wrote:
> How about you make the Quit menu item call a *different* method in your
> Application class, which performs the HTTP requests etc, and *then*
> terminates the applicaiton the usual way?
Well that sounds like a good idea but what happens if the App gets
quit from an AppleEvent or Logout or something? I think working
through the NSApplication quit system is going to make your app more
robust.
My guess, and it's just that because I haven't used thisstuff before
in any substantial way, is that the sheets run loop is interfering
here. I think you may find that the NSURLConnections are registered in
the NSApplications run loop - which doesn't get serviced during the
run of the sheet so you don't get your delegate methods called. The
existance of CFSocketCreateRunLoopSource leads me to believe this is
whats happening. For a quick test try making your sheet a separate
(non-modal!) window instead and see if it all works out. Anyway, I'm
not sure how to work around that but I think it may be whats going on.
Later,
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden