Hi Kevin, I'm definitely not calling it anywhere explicitly, but possibly by calling some other method.
My use of -runModalPrintOperation:delegate:didRunSelector:contextInfo: was passing nil for both delegate and the didRunSelector, which I thought might be the problem, but replacing those with a valid target and selector doesn't fix the issue (and without autosaving, the added run selector does run). What other methods could be a wrapper for -performActivityWithSynchronousWaiting:usingBlock: ? I should mention that I'm only using blocks very sparingly at the moment - just enough to overcome some deprecation warnings in things like NSOpenPanel; I don't use them extensively. Neither is my app very largely making use of threads, operation queues , GCD etc. It should be a pretty simple case. --Graham On 23/08/2011, at 12:32 AM, Kevin Perry wrote: > Graham, > > This can happen if there is a previous call to > -performActivityWithSynchronousWaiting:usingBlock: and the block never calls > the completion handler. If you use that method anywhere, please make sure the > completion handler always gets called. If you don't use the method directly, > other methods in NSDocument may call it and failure to invoke their > completion handlers properly may also result in these kinds of hangs. > > After checking these things, if you believe your code is not at fault, please > file a bug ASAP. > > -KP _______________________________________________ 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
