Hey Klaus,
I'm sorry my post can get a bit confusing, it's tough to explain over the internet
Anyway I think example programs seem to work well. First though, I do know that the developer has to make the app save itself because it took me some evenings to figure that out.
I made the first one like so...
When you open the app IN THE SIMULATOR you get the first stack and the button saves the Level Menu stack. Then you go into each level and press the big button. Next you go to the menu to see the numbers in the text fields, quit and reopen to verify that it saved. That's all you have to do for both programs.
Maybe I can explain my problem better.
How my app works is there are two cards, one Main Menu and one Level Select, and currently all the levels (25 of them) are substacks under the Main Menu just like in program 1.
The first program is the one i've been having the issues with. When I make the app with the levels (they're substacks) under the Menu, it won't save after you quit.
How it used to work is all the levels were under the Level Select and everything was saving fine. But if a player quit in the middle of a level all the apples (an element of my game) froze on the screen and became part of the background, thus adding more and more when you quit while playing. I tried using the code
but it didn't work. Do you know of a way to stop saving the progress of a substack so it doesn't leave the apples on the screen? From my reading so far I don't think there is a way but i'm not positive.
The second program is the one that works just fine it saves and everything is working perfect.
Should I check the box where it says "Move substacks into individual stack files?"
Now as far as I can see all the settings are the same but maybe you'll notice something or maybe something in my process isn't possible. Let me know.
As always, thanks for taking the time to help,
Danny