Good thought thanks Charles, but everything else seems to be responding as usual. No spinning wheel, still able to do other things in the UI. Main thread trace says:
#0 0x9546b0fa in mach_msg_trap () #1 0x9546b867 in mach_msg () #2 0x9212d37f in __CFRunLoopRun () #3 0x9212c464 in CFRunLoopRunSpecific () #4 0x9212c291 in CFRunLoopRunInMode () #5 0x92442f58 in RunCurrentEventLoopInMode () #6 0x92442d0f in ReceiveNextEventCommon () #7 0x92442b94 in BlockUntilNextEventMatchingListInMode () #8 0x96aa578d in _DPSNextEvent () #9 0x96aa4fce in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #10 0x96a67247 in -[NSApplication run] () #11 0x96a5f2d9 in NSApplicationMain () #12 0x00002d98 in main (argc=1, argv=0xbffff7d0) at /Users/gideon/Development/CADisplay/main.m:13 which I believe just means that it's idling, waiting for the next event. I tried running the whole thing without using a separate thread for that method, and it worked fine both the first and second time. Gideon On 08/12/2010, at 6:33 AM, Charles Srstka wrote: > On Dec 7, 2010, at 2:19 PM, Gideon King wrote: > >> Another data point on this: if I use waitUntilDone:NO, it doesn't even work >> the first time through. >> >> Responds to selector still returns YES. There are no error messages. > > Is something tying up the main thread? It won’t execute your request if it > doesn’t get to the end of its run loop. > > Charles _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
