site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Dec 18, 2008, at 2:54 PM, Micah Sharp wrote: Darrin -- Darrin Cardani dcardani@apple.com _______________________________________________ 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... I believe at one time, at least FCP I think, FxPlug IDs were not being honored, and in order to support backwards compatibility from one version to the next, you had to be sure to add all new UI at the end of your plug-in. Is this still the case? We're about to do a big update and this would be a bummer. There were a few issues that Paul could probably enumerate better than me. (Not sure if adding parameters works or not in FCP at this time.) However, nowadays, we do have the FxVersioning API which we make great use of internally. If you didn't include a version number in the Info.plist of your previous plugins, then documents containing instances created with the older versions will have a version of 0. If you add or increment the version in the Info.plist file, instances created with the new version of the plugin will return the new version number from the [FxVersioningAPI versionAtCreation] method. So you can tell if an instance was created with an older version or a current version. This email sent to site_archiver@lists.apple.com