Lab 6 of 7: Menu-Driven Applications (GUI) – (45 points)
L A B O V E R V I E W
Scenario/Summary
You will code, build, and execute two programs requiring GUI. The first program will ask the user to input a password and then reenter it for verification. The second program is a number guessing game that generates a random number and asks the user to input his or her guess.
Deliverables
Submit the following to this week’s Dropbox:
1. A zipped Visual Studio project folder for each programming exercise. Refer to the Deliverables section of the Week 1 iLab page for detailed instructions on how to zip a project folder.
2. A single MS Word file named YourLastName_Lab1_ex1.docx containing the following items:

• The source code for each program in the lab: Your source code should use proper indentation, include meaningful comments, and be error free. Start each with a specification that includes your name, the lab and exercise number, and a description of what the program accomplishes, similar to this:

/* Specification:
First Name Last Name
Lab 1 Exercise#
This program does X */
• Labeled screenshot(s) of the output windows for each program, showing that each program produces correct results

NOTE: A screenshot of a window can be created by first clicking on it to activate it. Next, press the key or key combination your specific computer uses to do a “print screen” (typically the Prnt Scrn or Prnt key in combination with the ctrl or FN key). Then, click the MS Word “paste” option to paste the screenshot into the MS Word file.
Objectives and Grading
Lab Objectives:
1. To be able to explain the need for menus in a program
2. To be able to determine ways to implement menus in a Windows application
3. To be able to understand the classes and objects used in a Windows application
4. To be able to write a Windows application
Your lab grade will be based upon:
1. the formatting of your source code;
2. the use of meaningful identifiers;
3. the extent of internal documentation; and
4. the degree to which an exercise’s specifications are met.
Preparation:

If you are using the Citrix remote lab, follow the login instructions located in the iLab tab in Course Home.
iLab Steps
Part A: Password Program
Requirements
Write a Windows application that simulates entering a password. The user enters a password and clicks Next. Then, the user types the password again and clicks Continue. The program will display a Message Box that displays either that the passwords match or that they don’t match.
Sample output:

I type in Bob in the password field and click Next.

I type in Bob in the second password field and click Continue.

Message displayed if the passwords match:

Message displayed if the passwords are different:

Tips
Best practice: First make sure to read through this week’s lecture and try it yourself! Then, you’ll be in good shape for this exercise.
Pseudocode:

Next Button Event Handler Method
• If the first password textbox is not blank

o Make visible the second password textbox, the Done button, and the labels
• Else

o Put “You must enter a password” in the label
• End-If
Done Button Event Handler Method
• If the first password text box is not empty

o If the first password text box equals the second password textbox

 Display the message “Passwords are the same”
o Else

 Display the message “Passwords are different”
o End-If
• Else

o Display the message “You must enter a password”
• End-If
END OF PART A

Part B: Number Guessing Game
Requirements
Write a Windows application that randomly generates a number from 0 through 100. Prompt the user to guess the number. Let the user know if the guess is too low, too high, or is the correct number. Give the user another chance to guess the number. The user keeps guessing until he or she gets it correct.

Sample output:

I entered a number and pressed the button.

I pressed the button and the box and message are cleared.

I entered a number and pressed the button.

After entering several numbers, I got the following:

The following message is displayed when the guess is right.

Tips
Pseudocode:

Form constructor method
• Randomly pick a target number between 0 and 100
Evaluate Button Click Event Handler Method
• If the guess text box is not blank

o Pull the guess from the text box
o Add 1 to the number of guesses
o If the guess is less than the target

 Make the Evaluate button invisible
 Change the label message to “Too Low!!”
 Make the label message visible
 Change the background color of the form to LightSeaGreen
 Make the Try Again button visible
o Else if the guess is greater than the target

 Make the Evaluate button invisible
 Change the label message to “Too High!!”
 Make the label message visible
 Change the background color of the form to SlateBlue
 Make the Try Again button visible
o Else

 Display a message indicating the user guessed correctly and display the number of guesses it took.
o End-If
• End-If
Try Again Button Click Event handler
• Clear the guess text box
• Make the label message and Try Again buttons invisible
• Make the Evaluate button visible
END OF PART B
END OF LAB