Re: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 Those are the only gotchas I can remember. _______________________________________________ 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... On 8/1/2011 12:56 PM, Eberhard Ammelt wrote: Thanks Paul, but both options don't help. It looks that the FxPlugWrapper object is the same for V1 and V2 parameter APIs. Hmm I don't know what to tell you. I know that some of the API interfaces look the same between v1 and v2. I just know that I also had the problem as you, and fiddling around with these 2 things helped. Make sure you are using FxParameterSettingAPI_v2 and FxParameterCreationAPI_v2, as well as FxParameterRetrievalAPI_v2. One more thing - when you create your Custom parameter, you *MUST* give it a default value. It can't be NULL. Even if it's just an empty NSData object, you have to pass something into the default value argument. This email sent to site_archiver@lists.apple.com
participants (1)
-
Paul Miller