Nov-18-2018, 04:46 PM
The first and most obvious thing is to stop using global. You want to be clear about what is going on in your functions. You do that with parameters and return values. See the function tutorial on how to do that.
The second thing is that this application really begs for classes. Take selectRotors. You have availableRotors and RotorsInUse, but neither of those contain rotors. They contain numbers pointing to rotors. So later on rather than just using the rotors, you have to use those numbers to find the rotors. With classes, availableRotors could just be a list of Rotor objects. When they select one, you could just remove it from availableRotors and put it in RotorsInUse, which would then be full of rotors. Check out the class basics tutorial for information on how to do that.
The second thing is that this application really begs for classes. Take selectRotors. You have availableRotors and RotorsInUse, but neither of those contain rotors. They contain numbers pointing to rotors. So later on rather than just using the rotors, you have to use those numbers to find the rotors. With classes, availableRotors could just be a list of Rotor objects. When they select one, you could just remove it from availableRotors and put it in RotorsInUse, which would then be full of rotors. Check out the class basics tutorial for information on how to do that.
Craig "Ichabod" O'Brien - xenomind.com
I wish you happiness.
Recommended Tutorials: BBCode, functions, classes, text adventures
I wish you happiness.
Recommended Tutorials: BBCode, functions, classes, text adventures