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 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. _______________________________________________ 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... This email sent to site_archiver@lists.apple.com