Actually, I tried NSModalPanelRunLoopMode first, but it didn't work; and I was not sure whether NSModalPanelRunLoopMode is exactly the mode of model panel's run loop. Then I thought since the modal panel's delegate method windowDidBecomeKey is called during runModalForWindow, the currentRunLoop must be modal panel's run loop, and currentMode of it must be the mode in which I wanted my connection's delegate methods called.
But it turned out that I still missed something here. On Tue, Dec 16, 2008 at 11:49 PM, Michael Babin <[email protected]>wrote: > On Dec 16, 2008, at 8:30 AM, [email protected] wrote: > > I want to handle the connection events during runModalForWindow, so I use >> [connection scheduleInRunLoop:[NSRunLoop currentRunLoop] >> forMode:[[NSRunLoop currentRunLoop] currentMode]]; >> in the modal window's windowDidBecomeKey delegate method. >> >> But still my connection's delegate methods are not called until stopModal. >> >> Is there anything I misunderstood about NSURLConnection's >> scheduleInRunLoop:forMode: method? >> > > Is there some reason not to pass in NSModalPanelRunLoopMode as the forMode > argument? What happens if you do? > > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
