Corona Tutorial: Display Objects and Texture Memory (Part 1)
In part 1 of this tutorial, I talk about the demo program used to explore Corona Display Objects and how it affects texture memory on mobile devices. I demonstrate how adding display objects (images) affects texture memory, and show the best practices for removing display objects to avoid app crashes.
You can download the Corona program used in this video here.
Posted at
12:13 pm, October 7th, 2010 in
Coding, Corona SDK, Corona Training, Tutorials, Videos | tags: development, display objects, how-to, lua, sdk, texture memory
RSS feed
Thanks for the great advice! I’m glad to see that it’s “Part 1″ of a series. When it comes to mobile app development, you really can’t optimize enough–so thanks again.
Long live BBEdit
There is something wrong with the image names. I have created Image1.jpg , 2 , 3 and the output is always
Image1 is not defined
image2 is not defined
image3 is not defined
solved (mistake was mine)
PS: “Image1.png” should be “Image1.jpg” in line 117
What if I generate images dynamically, I set a few additional properties to them (to an image/sprite object) and have them also referenced in a global table? What would be the right approach to remove them all from a display group and a global table? I do that in my project but I am getting a memory leaking and I can’t get rid of it. Help please.