Hi again, > hmm, that should happen once you destroy the image and the TextureChunk, > but only after the next frameExit (part of Window->render) call as in > order to destroy the OpenGL object one needs a valid context.
I don't destroy the TextureChunk and I think that destroying it would cause those memory leaks I was talking about in my other mail. Besides, I can't destroy the TextureChunk of a SimpleTexturedMaterial without destroying the whole Material, can I? > that was for destroying the OpenSG side (to free the image memory) > but keep the OpenGL side around for rendering. I see. Cheers and thank you Till ------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
