site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Brian, - Paul On Aug 8, 2009, at 6:47 PM, Brian wrote: Thanks for the tips, Steve. Actually, I am trying to save the state of a singleton object. (Neither per clip, nor global preference.) So, it's more like a 'project setting' type of thing. Or maybe even a 'sequence setting'. I'd certainly love it to be a 'sequence setting'. I'll definitely need to store the value inside the FCP (or Motion) project file, somehow. Any ideas? -- Brian _______________________________________________ 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/pschneider%40apple.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... the only "plugin state" that gets saved with the project is parameter data. As Steve says, you can use a hidden custom parameter to implement per-instance plugin state. There's no way to specify per-sequence or per-project state. Keep in mind that an FCP project can contain multiple sequences, and you can also have multiple projects open at once in FCP. I'm not sure how you could maintain a per-sequence or per-project singleton even in memory (since you don't know what project or sequence you're in), let alone save it with the project. This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com