Re: FCPX parameterChanged crash
On 2/4/2012 6:35 AM, Nathan Weston wrote: On 02/03/2012 02:23 PM, Paul Miller wrote: On 2/3/2012 12:12 PM, Darrin Cardani wrote: I don't have a definitive workaround. I believe that some people may have had some success by using an NSTimer to delay changing certain parameters, though I haven't tried that myself. As for the dialog hang, that is also fixed in a future release. I tried using an NSTimer - but when it fires you're outside of the event handling code for the button that triggered the change, so even if you're inside an action block you can see each parameter updating in sequence - and it doesn't undo properly. It's obvious GenArts got Edge to work - anyone have a clue how they did it? It wasn't pretty... we use performSelectorOnMainThread to move all the parameter setting into the main thread. I think this is basically equivalent to the NSTimer trick Darrin is suggesting, and has the same unpleasant side effects. We handle the extra renders by setting the output image to black and returning immediately -- so at least they go by relatively quickly. Undo still doesn't work correctly, but this seems to be the best that can be done at the moment. _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com Thanks for the tip Nathan - I had also tried performSelectorOnMainThread, and got similar results to using the timer. I didn't think about setting a flag to abort the render during the update though, which does take a long time (we have a lot more parameters I think). One other thing we noticed is now images we "check out" for the preview are now right-side up. But I believe they are still up-side down in Motion. Last I recalled, if we ask the API what host we're in, it always says Motion. Any ideas on working around that one? Weren't some plugins checking the application bundle's plist?
participants (1)
-
Paul Miller