If you can design the Invoice Total form that’s presented in this chapter, you’ve taken a critical first step toward learning how to develop Windows Forms applications with Visual Studio 2008. The next step is to add the code that makes the form work the way you want it to, and that’s what you’ll learn to do in the next chapter.
This exercise will guide you through the process of starting a new project and developing the user interface for the Invoice Total form shown in this chapter.
Start Visual Studio. If you want to change the import and export settings to make sure your menus are the same as the ones in this book, use Tools->Import and Export Settings command described in figure 2-1 to specify the default Visual Basic development settings.
Use the Tools->Options command to display the Options dialog box as shown in figure 2-1. Then, expand the Projects and Solutions group, select the General category, and change the Visual Studio projects location setting to C:\VB 2008.
If the Save New Projects When Created box and the Always Show Solution box aren’t checked, check them.
If you want to stop the Start Page from being displayed each time you start Visual Studio, click on Startup within the Environment group. Then, select another option from the At Startup drop-down list.
If you’re interested, take a few minutes to review the other options that are available in this dialog box. Then, close the dialog box.
Start a new project as shown in figure 2-2. The project should be named InvoiceTotal and it should be stored in the C:\VB 2008\Chapter 02 folder.
Add controls to the new form and set the properties
Use the techniques in figure 2-4 to add controls to the form so they have approximately the same sizes and locations as in figure 2-5. But don’t worry about the size of the labels, just their locations.
Select groups of controls and use the buttons in the Layout toolbar to size and align the controls. But here again, let the labels automatically size themselves. Then, size the form so it looks like the one in figure 2-4.
Use the Properties window to set the properties for the form and its controls so it looks like the form in figure 2-3. These properties are summarized in figure 2-8.
Use the View->Other Windows->Document Outline command to open the window for Document Outline view. Next, use this window to check that you’ve named all of the controls that have Name properties in figure 2-8. Then, click on the controls in this view to see what happens, and close this window when you’re done.
Test the user interface
Press F5 to build and run the project. That should display the form in the center of the screen, and it should look like the one in figure 2-3.
Experiment with the form to see what it can do. When you press the Tab key, notice how the focus moves from one control to another. When you click a button, notice how it indents and then pops back out just like any other Windows button control. Nothing else happens in response to these button clicks, though, because you haven’t written the code for them yet.
Notice that the Calculate button has a dark outline around it to indicate that its function will be executed if you press the Enter key. (If it doesn’t have a dark outline, you haven’t set the AcceptButton property of the form to the button.)
When you press the Alt key, notice that an underline appears under the s in the Subtotal, the first c in Calculate, and the x in Exit to indicate that you can use an access key to work with these controls. (If the underlines don’t show, you haven’t entered the Text properties correctly.)
If you notice that some of the properties are set incorrectly, click the Close button in the upper right corner of the form to close the form. Then, make the necessary changes and run the project again. When you’re satisfied that the form is working right, close the form to return to the Form Designer.
Experiment with the properties for the form and its controls
In the Form Designer, click on the form so it is selected. Then, if necessary, adjust the Properties window so you can see the description for each property. To do that, drag the bottom boundary of the window up.
Click on the Categorized button at the top of the Properties window to display the properties by category. Then, review the properties in the Appearance, Behavior, Layout, and Window Style categories. Although you won’t understand all of the descriptions, you should understand some of them.
In the Window Style category, change the settings for the MaximizeBox and MinimizeBox to False to see how that changes the form. Then, to undo those changes, click twice on the Undo button in the Standard toolbar or press Ctrl+Z twice.
Click on the first text box and review the Appearance, Behavior, and Layout properties for that control. Then, repeat this process for one of the labels and one of the buttons. Here again, you won’t understand all of the descriptions, but you should understand some of them.
Select all four of the labels, click on the plus sign before the Font property in the Appearance group, and change the Bold setting to True to see how that changes the form. Then, undo that change.
Change the name of the form files
Use one of the techniques presented in figure 2-9 to change the name of the form file from Form1.vb to frmInvoiceTotal.vb.
Note in the Solution Explorer that this also changes the name of the two subordinate files to frmInvoiceTotal.Designer.vb and frmInvoiceTotal.resx. To see these files, you may have to click on the Show All Files button and then on the plus sign for the frmInvoiceTotal.vb file.
Close the project and exit from Visual Studio
Use the File->Close Solution command to close the project. If you’ve made any changes to the project since the last time you tested it, a dialog box is displayed that asks whether you want to save the changes that you made. If you want to save those changes, click Yes.
Use the File->Exit command to exit from Visual Studio.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
