|
After adding a couple of sound effects triggered by left-clicking, I realised that I will have to remake the entire structure of the project, so as to include the various states.
This leads to another problem; using states without having to make it redundant. Right now my first state called INIT only reads from a file and returns the configuration to my Engine, while it’s supposed to be the initializer that starts up everything that is needed and then change the current state to READY, which is essentially the Main Menu area just before starting the actual game. While in theory this seemed like a good structure to build the game around, in reality I don’t see how it’s going to work with sending the program off to another class and leaving everything done in INIT behind…
What I could do is incorporate INIT into READY and calling the various methods from inside READY, although this is incredibly reduntant as it will accomplish the same thing as simply making a method Initialize in READY.
 
|