I've put this thread in Developer Support, but I guess it should be here as well.
My previous published app made 100% in CORONA SDK 1.0 without any modification stops working when it runs on SDK 1.01 and SDK 1.1
It seems some problem occurs in the latest versions of SDK where a previous debugged and running code stops working.
I would like to know what changes were made between these versions in order to understand where the problem can be, because it seems to be forwarding on new versions. I remember also that I've posted at SDK version 1.01 that my code stops working and here again on SDK version 1.1, but still running on SDK 1.0, interesting hum...?
Well, I hope someone from Ansca staff help me on this subject.
Regards,
Flavio.
I created an app with seven groups that do sound, video and pictures, and don't have the problem.
Flavio, could you send me code? info@anscamobile.com
carlos
Carlos,
Please read my post on Developer Request related to this subject.
I guess that could be more explanatory.
Flavio.
It seems to be related to child removal on display groups, which cause parent group goes to indeterminate state when you try to recharge childs objects on it.
I.e, after make a complete removal of children from the group, making child=nil it supposed to be group.numChildren = 0, so if you try to insert a new child, it will be inserted on position 1, making numChildren to be 1. But, when you verify numChildren you'll see a strange nil that produce a stack traceback.
This is something that is not evident on CORONA samples codes, because none of them remove and recharge a group over and over. All examples codes only runs one time, which means one time execution or cycle, let's say: load graphics, sounds and stuff then put on the screen and finally make activate some listeners to make animations and that's all.
When you try to make a hole game loop cycle with removal and reloading objects in a group you will encounter this problem.
Flavio.