site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 - Nathan _______________________________________________ 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... When I make a Motion Effect containing an FxPlug, it appears that it only stores parameters which have been changed from the default value. Is that expected behavior? This is a really bad idea. Consider the following case: 1. User creates a Motion Effect with version 1 of my plugin. They leave parameter X at the default value. 2. I release version 2 of my plugin, in which I've changed the default value of X to something nicer. 3. User installs version 2, and their Motion Effect now renders differently. In effect, it means we can never change parameter default values if we want to keep backward compatibility. If you store all the parameters in the Motion Effect it's guaranteed to render consistently even if the FxPlug changes default values underneath it. This email sent to site_archiver@lists.apple.com