Due Tuesday 7-Mar, at 10:00pm

---

Homework 7

To start

1. Create a folder named hw7
2. Inside that folder, create a file hw7.py. There is no starter file this week.
3. Download cmu_112_graphics.py to that folder
4. Edit hw7.p using Thonny, building the appropriate game. The file should contain all necessary code for the respective problem so that we can easily run and grade one problem at a time.
5. Submit hw7.py to Gradescope. For this hw, you may submit up to 999 times, but only your last submission counts.

Some important notes

1. This homework is solo. You may not collaborate or discuss it with anyone outside of the course, and your options for discussing with other students currently taking the course are limited. See the academic honesty policy for more details.
2. After you submit to Gradescope, make sure you check your score. If you aren’t sure how to do this, then ask a CA or Professor.
3. There is no partial credit on Gradescope testcases. Your Gradescope score is your Gradescope score.
4. Read the last bullet point again. Seriously, we won’t go back later and increase your Gradescope score for any reason. Even if you worked really hard and it was only a minor error…
5. Do not hardcode the test cases in your solutions.
6. The starter hw6.py file includes test functions to help you test on your own before you submit to Gradescope. When you run your file, problems will be tested in order. If you wish to temporarily bypass specific tests (say, because you have not yet completed some functions), you can comment out individual test function calls at the bottom of your file in main(). However, be sure to uncomment and test everything together before you submit! Ask a CA if you need help with this.
7. Remember the course’s academic integrity policy. Solving the homework yourself is your best preparation for exams and quizzes; cheating or short-cutting your learning process in order to improve your homework score will actually hurt your course grade long-term.

Limitations

Do not use sets, dictionaries, try/except, classes, or recursion this week. The autograder (or a manual CA review later) will reject your submission entirely if you do.

A Note About Style Grading

Like in the previous assignment, we will be grading your code based on whether it follows the 15-112 style guide. We may deduct up to 10 points from your overall grade for style errors. We highly recommend that you try to write clean code with good style all along, rather than fixing your style issues at the end. Good style helps you code faster and with fewer bugs. It is totally worth it. In any case, style grading already started, so please use good style from now on!

Problems

1. Midsemester Survey [5 pts]
   Take the midsemester survey linked from Piazza. Be sure to also fill out the second survey (linked at the end of the first) so that you get the points. The survey is due Monday, March 6 at 10:00pm.


2. MightyChess [95 pts, manually graded]

Extend the chess board that you made in hw5 with some animated features. You must satisfy the following requirements to get full credit:

• When the mouse left-click button is pressed inside a cell, and there's a piece of the player's color inside the cell, that piece is selected. Use the print function to indicate which row and col were selected, and if a piece was selected or not [ 8 points ]
• Your code MUST follow the MVC approach.
• Only one piece can be selected at any time. The selected piece must match the color of the player (black or white).
• When a piece is selected, the piece blinks (appears and disappears): it is visible for 0.5 seconds, and not-visible for 0.5 seconds. [8 points]
• When the mouse left-click button is pressed inside a cell that doesn't contain any piece, inside a cell that contains a piece of a different color , or outside the board, the currently selected piece is unselected. When any key except the keyboard arrows is pressed, the currently selected piece is unselected. Use the print function to report that the current piece was unselected. [ 8 points ]
• When a piece is selected, the user can move the piece up, down, left, or right using the keyboard arrows. The piece must continue to blink. [8 points]
• A selected piece cannot be moved to a cell that already contains a piece of the same color. [5 points]
• When the program starts, a splash screen is displayed with the following message [6 pts]

   Welcome to MightyChess
      Press s to start
      Press w to select the white pieces
      Press b to select the black pieces
  

• Implement the functionality of the intro screen (keys s, w, and b) [7 points]
• In the upper left hand corner of the screen is a timer. It counts from 60 seconds to 0 seconds, only displaying whole seconds. [7 points]
• After the 60-second timer has counted down to 0, the game stops and displays "Game Over" [5 points]
• If all pieces of different colors have been removed, the user wins. The game stops and displays "You Win". [5 points]
• When the user presses the Space Bar, a splash screen that covers the entire canvas is shown, with the word "Game Paused". The countdown timer also stops. [6 points]
• When the user presses the Space Bar when the game is paused, the game and the countdown timer should resume [7 points]
• A selected piece can be moved to a cell that already contains a piece of a different color. In this case, the other piece is removed from the board. [8 points]
• A selected piece cannot be moved outside the board. For instance, if the piece is located in the first row and the user presses the up arrow, it shouldn't move. [7 points]
• BONUS: After you have completed all the above points, you can earn up to 5 points as bonus by adding other animated features. Send an e-mail to the instructor at least 24 hours before the homework deadline with your ideas to get feedback about whether the features you plan to add are valid for bonus points.