Re: .moef parameter ids
Re: .moef parameter ids
- Subject: Re: .moef parameter ids
- From: Darrin Cardani <email@hidden>
- Date: Wed, 24 Aug 2011 13:44:13 -0700
On Aug 24, 2011, at 10:16 AM, Paul Miller wrote:
>> Oh, actually, I forgot, the parameters don't have to be in order. Here's a test I just ran:
> ...
>> 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.
>
> I'm still a little confused - because what you just showed is that the published parameter ids are still in creation order. I wasn't talking about moving them around in the project/publish settings (though this is a nice feature), but moving them around in the code itself. It seems if I add any control TO THE CODE before any other existing controls (so I can get the order I want in the Motion inspector, and in FCP7), it will break existing moefs because the ids used in the publishSettings section are in creation order, and not the actual code-defined ids.
OK, so, I've got some more information. I think what you want to do should still be possible. In the publishSettings element, you'll see target elements:
<target object="xyz" channel = "./1"/>
The xyz is the ID of your filter object in this document, and the "channel" attribute is the path, starting at your filter object, to the parameter you're publishing. For example, if you add the Spot Light Core Image filter to a Final Cut Effect, publish the "light position" and "light points at" parameters, and save it, you'll get these:
> <target object="10283" channel="./2"/>
> <target object="10283" channel="./3"/>
> <target object="10322" channel="./2/200"/>
> <target object="10322" channel="./2/201"/>
> <target object="10322" channel="./3/300"/>
> <target object="10322" channel="./3/301"/>
Channel 2 is the folder containing the channels for the position parameter. 2/200 is the position's (X,Y) value as a point parameter, and 2/201 is the position's Z value as a slider. Channel 3 is the "Light points at" folder, and 3/300 and 3/301 are the (x,y) and Z parameters for it. Does that make sense?
So, let's say you add a slider parameter #1 in the next version. If you want to publish it, you could output publishSettings that started with:
<target object="10283" channel="./1"/>
<target object="10283" channel="./2"/>
<target object="10283" channel="./3"/>
<target object="10322" channel="./2/200"/>
<target object="10322" channel="./2/201"/>
<target object="10322" channel="./3/300"/>
<target object="10322" channel="./3/301"/>
Or you could put it anywhere else in that list that you want. Everything should be just fine, regardless of where you put it either in the FxPlug, or in the publish settings.
Am I understanding what you want to do? Does that solve the problem? Existing .moefs should continue to work fine because they don't reference the new channel, and the other channels are referenced by their path within the effect, not their creation order.
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