site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi, Matt, - Paul On Sep 26, 2007, at 5:38 PM, Matt Rhodes wrote: Hey Team. Thanks a lot. Matt Rhodes Zaxwerks, Inc. _______________________________________________ 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... custom parameters work in FCP 6. You can use the SimpleMatte example, which uses custom parameters but no onscreen controls. We have FxPlugs that need to store some custom data along with the project (think of it as values in an Options dialog box). Using SimplePaint as an example, we've implemented an NSCoding object as a custom param. This works just fine in Motion 2 and Motion 3. I'm now trying to get this to work in FCP 6. But the - encodeWithCoder method doesn't get called when I save the file - so no custom data is saved. I noticed that SimplePaint doesn't work in FCP 6 (no onscreen controls, right?), so I can't debug by comparing results with that generator. Can someone please confirm or deny that the NSCoding objects are supported under FCP 6? Is there another recommended way to store custom data with a project? We have quite a bit of data to store - it can't exist as parameters. _______________________________________________ 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 This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com