coding formation, how should a code be built-up in "simple" terms, I see some codes go (map, sprite, button set) but some go (button, sprite, map) is there a "correct" set to optamize code, for FPS and MEM with lettle stress to the app?
Also i have seen some button codes get done as a gosub command, also before, in or after the main graphics sets, does any of this effect how the buttons work after being called?
This is something I was wondering about as well. I'm a complete novice on the subject but I would think sprites, buttons, and sound would all come before level design.
There is no "correct" way or standard in doing a certain program. It is up to the programmer to develop his/her own style and be comfortable with it. Choose a sample program and look at the way the code is organized. Some games I looked at are arranged by: Initialization, Main Program, Functions (input and output), Graphics (map and sprite), Sound, Data Arrays. Just don't load everything in...
Just don't load everything in one function call so that you can optimize FPS and Memory. Some debug information like FREEMEM function can also help you so that you can have a general idea of how much resource your program is using.
