site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Thunderbird 2.0.0.0 (Windows/20070326) I just heard about it. Awesome! (very happy with the FCP6 enhancements BTW). PS - see my bug report! :-) -- Paul Miller | paul@fxtech.com | www.fxtech.com | Got Tivo? _______________________________________________ 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... 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! This email sent to site_archiver@lists.apple.com