Re: .moef parameter ids
Re: .moef parameter ids
- Subject: Re: .moef parameter ids
- From: Darrin Cardani <email@hidden>
- Date: Wed, 24 Aug 2011 10:06:37 -0700
On Aug 24, 2011, at 9:58 AM, Darrin Cardani wrote:
> On Aug 24, 2011, at 9:54 AM, Paul Miller wrote:
>> It comes down to the root of my original question. The parameter ids in the "filter" section of the XML are by in-code ID - as I defined them in the code.
>>
>> The other parameter IDs for the published section are apparently from creation order, starting at 1.
>>
>> Lets say I have a parameter ID of 10 in the code and it's the first parameter I created. The published section will have it with an id of 1, and the filter section with an id of 10.
>>
>> Now in the future I add a new parameter with an id of 9 and put it before the original one. The previous control will now be the second one in the published list, not the first anymore. If I don't update the moef it seems it will think parameter id=10 is still the first parameter in the published section but instead parameter id=9 will be. I don't know how it's supposed to deal with that - I haven't tried it either :-)
>
> Oh, I see. Yeah, that seems like it would be a problem. I'll see if anyone here thinks differently (no pun intended).
Oh, actually, I forgot, the parameters don't have to be in order. Here's a test I just ran:
1) Create a new Final Cut Effect in Motion
2) Apply the Hue/Saturation filter to the effect source drop zone
3) Publish the Hue and Saturation parameters
4) Save the effect
5) Open the effect in a text editor and look for the "publishSettings" section. Note that the parameters are id=1 for Hue and id=2 for Saturation.
6) In Motion, click on the "Project" layer in the layer list and select the "Project" tab in the Inspector.
7) Drag the Saturation parameter so it's above the Hue parameter
8) Save
9) Re-open the effect in a text editor and look for the "publishSettings" section. Note that now the Saturation is first, but its id is still 2, and Hue is second, but its id is still 1.
So it shouldn't be a problem. You should be able to insert a new parameter above the old one, but with a higher ID.
Darrin
--
Darrin Cardani
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