site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 On Aug 24, 2011, at 8:46 AM, Paul Miller wrote: I'm trying to make some sense of the parameter IDs in the .moef files, since I am writing some code to generate about 250 of them. In the publishSettings and sceneNode elements, parameters seem to have ids based on their created index (ie. they start at 1). But in the filter element parameters have ids that match the ids I gave them in the code. I'm not sure I fully understand what you're asking. Are you trying to publish some of your FxPlug's parameters based on the values of some of the scene node's parameters? For example, if the scale of an element is over 50%, then publish your plug-in's color parameter, or something like that? The Motion XML format is described here: <http://developer.apple.com/library/mac/#documentation/AppleApplications/Conceptual/motion_XML_guide/Overview/Overview.html> I'll do my XML edits by parameter name instead - bypass the whole issue. _______________________________________________ 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/24/2011 11:24 AM, Darrin Cardani wrote: How can I relate one to the other? (since I want to publish some of them depending on the values of other parameters). Generally, scene nodes have IDs that are sequential because the user can create any number of them, but their parameters have fixed IDs. For example, Transform is always id 100 and Position id 101, I believe. Ok I understand the sequential part of it. But it does mean if I add a parameter to an FxPlug later it'll mess up the published list, right? This email sent to site_archiver@lists.apple.com