site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com You're right; the closest thing would be FxBitmap. Dave On Jul 3, 2007, at 5:16 PM, Garrick Meeker wrote: _______________________________________________ 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... Sorry, there's nothing like a memory suite in the FxPlug SDK at present. It is something we know would be a good addition some day. Realistically, there are plenty of other demands on RAM outside of the app's purview. So depending on how much memory you're talking about, you might just get by with malloc(). 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