While the program runs pretty smoothly while testing "in one go" (aka not closing the program) in terms of changing labels,button names, tooltips, and disabling/enabling, once you close the program and then rerun the program, everything reverts back to the pre-game states.
Checks (if statements, etc.) need to be made/added to the "initialization" methods and constructors so that program states are being held no matter what has happened to the program.
For example, once you get to the final week, the general panes' "advance week" button changes to "advance final week", yet if you close the program during the final week, once you reopen it, it's reverted back to the old text of "advance week".
While the program runs pretty smoothly while testing "in one go" (aka not closing the program) in terms of changing labels,button names, tooltips, and disabling/enabling, once you close the program and then rerun the program, everything reverts back to the pre-game states.
Checks (if statements, etc.) need to be made/added to the "initialization" methods and constructors so that program states are being held no matter what has happened to the program.
For example, once you get to the final week, the general panes' "advance week" button changes to "advance final week", yet if you close the program during the final week, once you reopen it, it's reverted back to the old text of "advance week".