site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Darrin, Hmm, on second thought, this regenerates the data each time the project is opened, which is less than optimal. It's potentially very expensive to generate this particular custom data, so I'd prefer to do it only once. For example, imagine computing optical flow for the clip. Currently I'm checking out the first frame as a bitmap and reading a few bytes to make sure they match the stored values. However, this is obviously stupid, because two different clips might have identical first frames. I would add a "Regenerate" button using the custom UI, but then that rules out FCP X. Any other ideas? Ben On Nov 28, 2011, at 11:23, Darrin Cardani wrote:
Ben, Each plug-in instance has their -initWithAPIManager: method called, regardless of how they're created. Maybe you could do something like have a singleton which doles out custom IDs, and call it in the -initWithAPIManager: method. Then, whenever you go to use the custom data, if the id for that data doesn't match the id generated in -initWithAPIManager:, you throw it out and generate unique data for it. Would that work?
Darrin
_______________________________________________ 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