Re: FCP 6.0.3 and FxCustomParameterAction updates
Re: FCP 6.0.3 and FxCustomParameterAction updates
- Subject: Re: FCP 6.0.3 and FxCustomParameterAction updates
- From: Paul Schneider <email@hidden>
- Date: Wed, 14 May 2008 14:14:44 -0400
Hi, Pauli,
there were very few FxPlug-related changes in Final Cut 6.0.3, and I'm
not aware of any that might have caused a difference in our behavior
here.
I wrote a very simple FxPlug filter that manages its own floating
Cocoa window, with a button in the window to trigger a redisplay. It
seems to work correctly in 6.0.3. I've attached it - if it works on
your systems, perhaps you can spot a difference between this plugin
and what you're doing?
Also, when you say "we're receiving reports", do you mean that you've
tested your plugin in 6.0.3, and something that always used to work
now always fails? Or do you just mean that some of your customers are
reporting problems?
Thanks,
- Paul
Attachment:
FloatingWindow.zip
Description: Zip archive
On May 14, 2008, at 8:18 AM, Pauli Ojala wrote:
Hello,
I'm hoping someone on the FCP FxPlug team might be able to give some
insight into a problem that our users have been experiencing.
Our plugin Conduit uses a private Cocoa window for its nodal effect
editor UI. When the user modifies something in the editor window, we
use FxCustomParameterActionAPI and FxParameterSettingAPI to set a
new value for a custom parameter on the FxPlug instance. Ever since
Motion 2.0, this method has worked fine for triggering a render in
the host application. This way we don't need to run the editor
modally; the user can keep the window open while moving around on
the host app's timeline, which is very convenient.
Now we're receiving reports that the FCP 6.0.3 update has broken
this behaviour. Apparently the Viewer doesn't update anymore in
response to events in our editor window. However, one user mentioned
that switching from FCP to Finder and then back to FCP does trigger
the expected render in the Viewer in FCP. So it sounds like the
problem might be some fairly trivial bug somewhere -- as in the
viewer not getting the equivalent of [-NSView setNeedsDisplay:]
after the FxPlug parameter has been modified...?
Pauli Ojala
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden