Jan-04-2023, 09:15 PM
I wanted to put all the drawing code in one place. When the only thing drawn in a screen update was the cube, it made some sense to have Cube.draw() do the entire update. Now a screen update flood fill's the screen, draws the cube, and draws a message. I already felt a little guilty about having Cube.draw() doing the flood fill, but having it also draw a message, well it is just not good design.
I wrote a new screen_refresh() function that does all the things needed to refresh the screen. When I did that, the only thing Cube.draw() did was call Square.draw() for each of the squares. That isn't much to do, and Cube.draw() was only called from one place, so I incorporated the square drawing loop from Cube.draw() into screen_refresh(). You may have noticed that earlier I did the same thing with Cube.rotate() and Cube.move().
Now with a dedicated screen_refresh() function you have a logical place to put code if you wanted to add a score keeper or add an animation, or any kind of visual function that has nothing to do with cubes or squares or game play.
As written, there is a short delay between the player's move and the robot's move. If you want that delay to be longer you can use wait(), but that just seems silly. If you want the robot player to be slower, remove the alpha/beta pruning in minimax. Personally, I don't understand why you would want to make your player have to wait for the robot.
I wrote a new screen_refresh() function that does all the things needed to refresh the screen. When I did that, the only thing Cube.draw() did was call Square.draw() for each of the squares. That isn't much to do, and Cube.draw() was only called from one place, so I incorporated the square drawing loop from Cube.draw() into screen_refresh(). You may have noticed that earlier I did the same thing with Cube.rotate() and Cube.move().
Now with a dedicated screen_refresh() function you have a logical place to put code if you wanted to add a score keeper or add an animation, or any kind of visual function that has nothing to do with cubes or squares or game play.
As written, there is a short delay between the player's move and the robot's move. If you want that delay to be longer you can use wait(), but that just seems silly. If you want the robot player to be slower, remove the alpha/beta pruning in minimax. Personally, I don't understand why you would want to make your player have to wait for the robot.