Updated TODO

todo.txt

@@ -1,8 +1,9 @@
 1. Try to make the ball go between screens.
-3. ----SHOULD BE DONE---- Add code to zip the dist/ folder inside the release_build script.
+2. ----SHOULD BE DONE---- Add code to zip the dist/ folder inside the release_build script.
-4. Sign Windows executable, to remove 'Unknown Publisher' warnings.
+3. Sign Windows executable, to remove 'Unknown Publisher' warnings.
-5. Remove debugging print statements.
+4. Remove debugging print statements.
-6. Create and publish statically-linked Linux binary, and create a build script for packaging it.
+5. Create and publish statically-linked Linux binary, and create a build script for packaging it.
-7. Figure out how to build statically-linked Mac binary, and create a build script for packaging it.
+6. Figure out how to build statically-linked Mac binary, and create a build script for packaging it.
-8. ----IN PROGRESS---- Figure out how to input game mode and (if applicable) IP address and port through the GUI, instead of the command-line.
+7. ----IN PROGRESS---- Figure out how to input game mode and (if applicable) IP address and port through the GUI, instead of the command-line.
-9. Clean up / refactor the raygui code in main.cpp, that asks user for game mode. Instead of just having a giant blob of code in main.cpp, maybe split it into a function, or move it to another file.
+8. Clean up / refactor the raygui code in main.cpp, that asks user for game mode. Instead of just having a giant blob of code in main.cpp, maybe split it into a function, or move it to another file. It should be easy to split it into a different function, since none of the functions take any specific parameters. The text box function, for example, only takes in the rectangle coordinates, and the text to display. I can move the code to a function, and then pass in any parameters that I need to pass in (I don't think I need to pass many parameters, though).
+9. Allow the user to quit before the game actually starts i.e. while they are inputting the game mode.