I need to be able to access a whole bunch of values globally. Which technique of bringing them global is the most stable?
Just making the objects global crashed the game consistently.
Also, is there a way to "freeze" all the object and counter values in a frame while going to a different frame for a couple of seconds? Or do I have to copy everything over in INIs to make it really stable?
I find it hard to believe that it was global objects causing the crash, did you actually completely narrow it down to the crash being caused by them?
Personally, i would use one of the array objects to save data between frames.
Alternatively, do everything in the same frame. From what you describe it sounds like you just want to build a menu or inventory or something similar? It's perfectly possible to create that inside the main game frame. Just remember to pause your game and bring up the menu on a higher layer, then resume the game when the play exits the screen!
Yeah, I pretty much isolated the problem to making the active objects global holding the buying and selling information in the menu frame. When the only modification I make is them non-global, I can jump from the menu frame and the level frame without problems. When they are global, I can only jump to the menu frame once and back. The next time, the app will crash.
I had the menus in the level before, but the menus grew too complex to be worth it.
example :
Hmm, think I solved the problem. I had a couple of Magic Deques global in the level frame which caused the program to crash when re-entering the level. I don't need them global anyways since the current level automatically pauses with this awesome sub-application thing.
Too bad though I can't seem to have anything at all global
I personally have never had a problem with global things. It might be the way you're using them as opposed to them actually being global. All the crashes i've had in MMF have been my fault rather than MMF.
Advertisement
Post Reply
Edited by the Author.
