Jan-03-2023, 07:21 PM
(This post was last modified: Jan-03-2023, 07:21 PM by deanhystad.)
Do you think about what you are doing first, or do you immediately start coding? This is an easy problem to solve if you think about what it means to refresh the pygame screen.
You can think of pygame as having two screens. The one you see and the one you draw on. I'll call the screen you draw on as the "backing screen" and the one you can see the "visible screen". After drawing to the backing screen you call display.flip() (or display.update()) to draw the backing screen to the visible screen.
To normal way to refresh the screen in pygame starts with erasing the backing screen or drawing a full screen background. Next you draw all the objects you want to appear on the visible screen. After everything is drawn on the backing screen you flip the visible screen to display the backing screen. This is how cube.draw(surface) works. Every time cube.draw(surface) is called, anything previously drawn to the backing screen gets erased.
Your code has two problems. The first problem is you are not drawing the text when the game is over. You draw your message when the player resets the board. This is when the board gets reset and the cube is redrawn. What you should do is check cube.done() after calling cube.play(). If the cube is done you know it is the result of the last play.
The second problem is that you refresh the screen immediately after you draw the text. cube.draw(surface) is called each time there is a MOUSEBUTTONDOWN event. This erases your text before anyone has a chance to see it. If you want text to remain on the screen you need to draw the text after the screen is refreshed or add drawing text to the refresh function. Either will work, but I prefer the latter. I like keeping all the screen drawing code in one place instead of sprinkling it around throughout the program. It makes it easier to control the drawing order. You want to draw the message after drawing the cube. You want to draw the cube after drawing the background.
You can think of pygame as having two screens. The one you see and the one you draw on. I'll call the screen you draw on as the "backing screen" and the one you can see the "visible screen". After drawing to the backing screen you call display.flip() (or display.update()) to draw the backing screen to the visible screen.
To normal way to refresh the screen in pygame starts with erasing the backing screen or drawing a full screen background. Next you draw all the objects you want to appear on the visible screen. After everything is drawn on the backing screen you flip the visible screen to display the backing screen. This is how cube.draw(surface) works. Every time cube.draw(surface) is called, anything previously drawn to the backing screen gets erased.
Your code has two problems. The first problem is you are not drawing the text when the game is over. You draw your message when the player resets the board. This is when the board gets reset and the cube is redrawn. What you should do is check cube.done() after calling cube.play(). If the cube is done you know it is the result of the last play.
The second problem is that you refresh the screen immediately after you draw the text. cube.draw(surface) is called each time there is a MOUSEBUTTONDOWN event. This erases your text before anyone has a chance to see it. If you want text to remain on the screen you need to draw the text after the screen is refreshed or add drawing text to the refresh function. Either will work, but I prefer the latter. I like keeping all the screen drawing code in one place instead of sprinkling it around throughout the program. It makes it easier to control the drawing order. You want to draw the message after drawing the cube. You want to draw the cube after drawing the background.