Re: .moef parameter ids
Re: .moef parameter ids
- Subject: Re: .moef parameter ids
- From: Darrin Cardani <email@hidden>
- Date: Wed, 24 Aug 2011 09:58:50 -0700
On Aug 24, 2011, at 9:54 AM, Paul Miller wrote:
>> It shouldn't mess up the published list if you add an FxPlug parameter later. What makes you think that? (I haven't actually tried it - but I can't think of anything that would mess it up.) As always, if you do add parameters later, just make sure you use versioning (via the FxVersioning API) so you can recognize older instances of your plug-in.
>
> 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).
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