FCP 6.0.3 and FxCustomParameterAction updates
FCP 6.0.3 and FxCustomParameterAction updates
- Subject: FCP 6.0.3 and FxCustomParameterAction updates
- From: Pauli Ojala <email@hidden>
- Date: Wed, 14 May 2008 15:18:06 +0300
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