site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com We've been doing this: Micah _______________________________________________ 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/micah%40redgiantsoftware... This email sent to micah@redgiantsoftware.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... FxBitmap* pNewInputImage = [[FxBitmap alloc] initWithInfo:(FxImageInfo)outImageInfo]; ----- Original Message ----- From: "Garrick Meeker" <garrick@digitalanarchy.com> To: <pro-apps-dev@lists.apple.com> Sent: Tuesday, July 03, 2007 5:16 PM Subject: FxPlug memory allocation Is there a recommended way of allocating memory in an FxPlug? We have a very memory hungry plugin and I'm worried about the host app's image caches. I don't see anything like After Effect's memory calls. I suppose I could allocate FxBitmaps for non-image purposes, but is there a better way? This email sent to site_archiver@lists.apple.com