Dear all,
I need to apologize because I am far from the forum. I’m working on 3 different jobs on the same day. I don’t have time to answer your questions in the forum or by e-mail, I’m really sorry about that. As soon as I can, I will be pleased to answer everything again as I used to.
We have great developers here and I’m seeing a lot of good answers on my subscription to this forum by e-mail. I think most of you can handle your issues following this steps:
1 - Are your display objects inserted into the localGroup? If not then the objects will stay on the screen. To work properly you have to insert all display objects into the localGroup.
2 - Are you using big images? Try to export them with “Save for web & devices” at Photoshop.
3 - Is there too many images loading at the same time? Please take care to load images lazy, otherwise the app will crash on the device.
4 - Is there any button at the same position of other button in the next scene? With that there can be an issue on faster touchs just because the buttons are in the same place.
5 - Have you made a search for the issue at the forum? Most of your doubts may have been previously resolved, please search for it before creating another topic.
6 - There are great examples made by Beebe Games and other developers at the Code Exchange page. You can find there great ways to build your games.
7 - If you want to make a book, please keep in mind that your images probably will be big and the app will not load them in a second.
8 - Director cleans display objects and the listeners added to them. It can’t clean timers and Runtime listeners, that’s why the clean() function exists. You have to put there the Runtime:removeEventListener()s, timer.cancel()s and stop the transitions.
9 - The sample from v1.2 is not so different of the v1.1, it is just more organized.
10 - The initVars() function was created to start the VALUES of your variables, so you can use it to start the level or replay it. [import]uid: 8556 topic_id: 7305 reply_id: 307305[/import]