Re: FxPlugs UI in FCP and Motion different
Re: FxPlugs UI in FCP and Motion different
- Subject: Re: FxPlugs UI in FCP and Motion different
- From: Paul Miller <email@hidden>
- Date: Sun, 29 Apr 2007 18:22:37 -0500
Dave Howell wrote:
Supervising (setting a param in response to user changing some other
param)
Yes in both. There were some restrictions here in earlier versions.
Details can be found in the FxHostCapabilities.h header.
Note - I found the case where a control could not be changed in response
to its own change. Ie you fiddle with a popup control and your update
code sets it to a different state. Easily worked around with custom
NSViews, but this "works" in AE.
As you understand this is a request to make the FxPlug implementations
of Motion and FCP to behave the same, and for now, let me know the
differences so I can make good UI's for the users.
And thanks for using the public list!
I just heard about it. Awesome!
(very happy with the FCP6 enhancements BTW).
PS - see my bug report! :-)
--
Paul Miller | email@hidden | www.fxtech.com | Got Tivo?
_______________________________________________
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