site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Jun 30, 2011, at 10:23 PM, Garrick Meeker wrote:
Are there any threading issues to consider when combining FxProgressAPI and performSelector in FxHostResourcesAPI? When I had to do my own threading, I made sure on job was on the main thread so FxProgressAPI would work, and then signal the other threads to abort. Can any thread now call userHasCancelled? Does it matter which thread calls updateProgress?
I haven't noticed any issues, except that FCP doesn't seem to use this. For a really slow plugin (like a debug build) it seems to beachball yet userHasCancelled always returns NO.
There shouldn't be any threading issues to worry about when calling -updateProgress. For -userHasCancelled, it's probably a good idea to make sure any of your threads that could call it are all stopped before returning from your render method because the control object that handles aborting a render gets modified after a render is complete (or aborted). But during the render, any of them should be able to call it safely. Darrin -- Darrin Cardani dcardani@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com