Testing the OutlookBar Control
Testing the OutlookBar ControlTesting the final control is a victory that should be savored. The various controls, components, and designers for the OutlookBar control and its related controls demonstrate the basic requirements for creating custom controls for Windows Forms. Figure 9.3 shows the test application displaying a MessageBox indicating which item was clicked on. Figure 9.3. The OutlookBar client.
To test the OutlookBar control, compile the solution containing all the code developed thus far. This will result in the dll SAMS.ToolKit.dll being created. This dll houses all the components, controls, and designers developed to this point. Creating the client application requires starting a new Windows Forms project and adding the OutlookBar and ImageListView controls to the Toolbox. Adding the controls to the Toolbox requires customizing the Toolbox and browsing to the location of the newly compiled dll. To create the test application, drag the OutlookBar control onto the main form. Next, drag an ImageListView control onto the OutlookBar control. A new tab is automatically created. Associate an ImageList component with the ImageListView control containing a set of large images. The images can be of anything. The images shown in Figure 9.3 were borrowed from Microsoft Outlook. After the ImageList has been associated with the ImageListView control, use the Items property editor to add ImageListViewItems and set the text and image index for them. Listing 9.5 shows the result of the test client code. Listing 9.5 OutlookBar Client 1: using System; 2: using System.Drawing; 3: using System.Collections; 4: using System.ComponentModel; 5: using System.Windows.Forms; 6: using System.Data; 7: 8: namespace OutlookBar_Test 9: { 10: /// <summary> 11: /// Summary description for Form1. 12: /// </summary> 13: public class Form1 : System.Windows.Forms.Form 14: { 15: private SAMS.ToolKit.Controls.OutlookBar outlookBar1; 16: private System.Windows.Forms.ImageList LargeImages; 17: private SAMS.ToolKit.Controls.ImageListView imageListView1; 18: private SAMS.ToolKit.Controls.OutlookBarTab outlookBarTab1; 19: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem1; 20: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem2; 21: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem3; 22: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem4; 23: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem5; 24: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem6; 25: private SAMS.ToolKit.Controls.ImageListViewItem imageListViewItem7; 26: private System.ComponentModel.IContainer components; 27: 28: public Form1() 29: { 30: // 31: // Required for Windows Form Designer support 32: // 33: InitializeComponent(); 34: 35: // 36: // TODO: Add any constructor code after InitializeComponent call 37: // 38: } 39: 40: /// <summary> 41: /// Clean up any resources being used. 42: /// </summary> 43: protected override void Dispose( bool disposing ) 44: { 45: if( disposing ) 46: { 47: if (components != null) 48: { 49: components.Dispose(); 50: } 51: } 52: base.Dispose( disposing ); 53: } 54: 55: #region Windows Form Designer generated code 56: /// <summary> 57: /// Required method for Designer support - do not modify 58: /// the contents of this method with the code editor. 59: /// </summary> 60: private void InitializeComponent() 61: { 62: this.components = new System.ComponentModel.Container(); 63: System.Resources.ResourceManager resources = new Listing 9.5 is 99% generated during the design process of the test application. The only hand-coded method is the imageListView1_ItemClicked event handler on line 163, and even the stub for this was genereated by double-clicking on the ImageListView control. The imageListView1_ItemClicked event handler uses the ImageListViewEventArgs parameter to get the text of the ImageListView item and displays a message box stating which item was clicked on. Of 168 lines of code, only 2 lines have to be typed. Isn't code generation wonderful? |
System.Resources.ResourceManager(typeof(Form1)); 64: this.outlookBar1 = new SAMS.ToolKit.Controls.OutlookBar(); 65: this.LargeImages = new System.Windows.Forms.ImageList(this.components); 66: this.imageListView1 = new SAMS.ToolKit.Controls.ImageListView(); 67: this.outlookBarTab1 = new SAMS.ToolKit.Controls.OutlookBarTab(); 68: this.imageListViewItem1 = new SAMS.ToolKit.Controls.ImageListViewItem(); 69: this.imageListViewItem2 = new SAMS.ToolKit.Controls.ImageListViewItem(); 70: this.imageListViewItem3 = new SAMS.ToolKit.Controls.ImageListViewItem(); 71: this.imageListViewItem4 = new SAMS.ToolKit.Controls.ImageListViewItem(); 72: this.imageListViewItem5 = new SAMS.ToolKit.Controls.ImageListViewItem(); 73: this.imageListViewItem6 = new SAMS.ToolKit.Controls.ImageListViewItem(); 74: this.imageListViewItem7 = new SAMS.ToolKit.Controls.ImageListViewItem(); 75: this.outlookBar1.SuspendLayout(); 76: this.SuspendLayout(); 77: // 78: // outlookBar1 79: // 80: this.outlookBar1.Location = new System.Drawing.Point(24, 24); 81: this.outlookBar1.Name = "outlookBar1"; 82: this.outlookBar1.Size = new System.Drawing.Size(112, 216); 83: this.outlookBar1.TabIndex = 0; 84: this.outlookBar1.Tabs.AddRange(new SAMS.ToolKit.Controls.OutlookBarTab[] 
EAN: 2147483647
Pages: 74