One thing I do a lot is to load multiple images iterating over tables using a for loop. Following that in the code, there might be an animation involving the images just loaded. But as we already know, the app will freeze while the images are loading. Then when the app returns, the next bit of code, say animation, has already started. That’s understandable, the for loop iterates immediately and then the next thing executes, in between that Corona is busy loading in images…
This can be seen again using certain composer scene transition effects that require two scenes to be in memory e.g. “crossFade”. When you goto a new scene with crossFade, the alpha transitions are called within the crossFade effectList at the same time as the next scene is created so you get the freeze and then the next scene pops on. You might get a little of the crossFade effect at the end if you’re lucky - depends on how many images Corona is busy creating.
I’m not asking how to solve the freeze thing. It happens, it’s a consequence of Corona working on top of a native process I guess. But what work-arounds do we have?
Specifically is there some way to know when an image has loaded? That way the app can wait until the images have loaded before starting the next instructions.