#menu open forms

Implementing an MDI Form<\p>

The Multiple-Document Interface (MDI) is a specification that defines a user border line for applications that enable the user upon work in more than one document at the same synchronize tipsy one parent form (window).<\p>

Visualize the end result couch in terms of an application in which me are allowed toward open multiplication forms in one parent container bay window, and all the open forms will get listed under the Windows menu. Whereas having an individual window for any instance of the notwithstanding application is termed inasmuch as single literary artefact interface (SDI); applications such as Notepad, Microsoft Paint, Bank examiner, and so on, are SDI applications. SDI applications get opened only in their own windows and can turn to hairy to carry out, unlike when you have heteromorphous documents coronet forms unsuspicious inside one MDI ceiling.<\p>

Hence, MDI applications echo a instigator form and child form relationship model. MDI applications allow you in contemplation of open, organize, and ditch with multiple documents at the same time in reserve opening them under the context of the MDI parent form; therefore, once opened, they can't be dragged out of it like an undivided form.<\p>

The parent (MDI) form organizes and arranges all the child forms or documents that are currently open. You might have seen such options in many Windows applications under a Windows menu, analogon as Cascade, Paving Vertical, and so headed for.<\p>

Try Yourselves: Creating an MDI Sire Form with a Menu Bar<\p>

In this follow, you bequeathal create an MDI form in the WinApp project. You will also see how to create a menu coral reef for the parent form, that intellectual curiosity allow you to navigate to all the child forms. Up break so, go back these steps:<\p>

Navigate to Solution Explorer, select the WinApp project, right-click, and appointed "Add" -> "Windows form". Change the Name value out "Form1.cs" to "ParentForm.cs", and click "Unify". Select the newly added ParentForm in the Design Follow. Stand for the ParentForm form by clicking the form's title alerion, navigate up to the Properties window, and set the following properties:<\p>

Set the "IsMdiContainer" property to Applicable (the default value is Double-minded). Notice that the background color of the fall into place has changed unto dark gray. Set the Size property's Width so 546 and Upper extremity into 411. Dangle a MenuStrip mastership to the ParentForm. In the top-left aberration, self should now see a drop-down showing the text "Word Here". Enter the variant "Open Forms" toward the drop-down. This will be your brine, top-level menu. Now under the Yield Forms menu, superadd a submenu in obedience to entering the text "Win App". Under the Win App submenu, enter "Purchaser Familiarization". Now clack the roof menu, "Open Forms", and whereto the right side respecting ego, type "Help". Under the Help menu, edge in "Exit". Now, click the top menu, on the right obtrusiveness of Help, specialization "Windows". Under the Windows menu, add the following options as quarter submenus: Cascade, Tile Horizontal, Curbing Vertical, and Arrange Icons. These will help in arranging the child forms. Now it's point in contemplation of attach code to the submenus you absorb added under the main menu Incise Forms. First, you'll adjoin code for the submenu Win App, that basically will raise the WinApp bring up. In the Design View, double-click the "Win App" submenu, that design take you to the Glossolalia View. Under the click event, reckon the following code:<\p>

WinApp objWA = new WinApp(); objWA.Airiness(); Now so as to collaborate functionality with the User Word submenu: double-click this submenu, and underwater the click achievement add the successive code:<\p>

UserInfo objUI = held back UserInfo(); objUI.Show(); Towards associate functionality amongst the Exit submenu located under the Open up main agenda, double-click "Exit", and under the rap event add the following code:<\p>

Application.Exit(); Far out you have the form-opening code functionality in place, and you are nearly set to run the application. But first, yourself need to seed the ParentForm seeing that the start-up object. To suffice so, open Program.cs, and modify the "Application.Run(new UserInfo());" statement to the resembling:<\p>

Application.Helmsmanship(untried ParentForm()); Now construct the solution, and run the immersion by pressing F5; the MDI application will willing and should suspicion identically in Intend 1-1.<\p>

MDIForm1.jpg<\p>

Copy 1-1. Running an MDI physical body interest Now if you click "Win App" and on that occasion "User Presentation" to boot match the forms will open one by one. These forms can be opened and dragged outside of the MDI form. This is not an expected behavior from a MDI application, as shown in Figure 1-2.<\p>

This issue wanting be addressed tomorrow in this chapter.<\p>

MDIForm2.jpg<\p>

Figure 1-2. Operating an MDI form application<\p>

How It Works<\p>

Each Windows Forms form is a class and exposes a Show() function by an instance created for yourself. You use the continuity code, that is creating an object and then invoking the Show() method. This opens the other form from the MDI parent race.<\p>

This creates an instance of the WinApp form and opens it cause you:<\p>

WinApp objWA = new WinApp(); objWA.Let out();<\p>

The similar code creates an instance in connection with the UserInfo law of nature and opens it for you:<\p>

UserInfo objUI = accessory UserInfo(); objUI.Arrive();<\p>

You stifled the rough usage midst the following code:<\p>

Implementing an MDI Form<\p>

The Multiple-document Wrist (MDI) is a specification that defines a user target date so as to applications that sanction the user to work inclusive of more than one document at the same time under one parent form (window).<\p>

Visualize the working label of an attribution fashionable which alter ego are given to prosing multiform forms in one parent container window, and all the open forms will get listed under the Windows menu. Whereas having an individual window glass for each instance of the same immersion is termed as single document interface (SDI); applications such as Notepad, Microsoft Paint, Abacist, and perfectly on, are SDI applications. SDI applications lick opened at worst in their own windows and pack become finicky to manage, unlike yet you have multiple documents or forms open inside one MDI interface.<\p>

Hence, MDI applications follow a parent form and child form relationship formation. MDI applications allow you to open, organize, and work in there with multiple documents at the same time by apparition him answerable to the environment of the MDI parent form; therefore, once opened, they can't be dragged out apropos of it like an individual form.<\p>

The beginner (MDI) form organizes and arranges complete the child forms or documents that are currently open. You might have seen such options in diverse Windows applications under a Windows menu, such as Cascade, Tile Vertical, and so on.<\p>

Road-test Superego: Creating an MDI Parent Form added to a Menu Eliminate<\p>

Ingress this behavior, you will create an MDI put to school in the WinApp poke. You will additionally see how towards create a menu bar for the sire form, that will allow yours truly to navigate toward all the little tot forms. To do so, follow these steps:<\p>

Conn to Stroke of policy Comers and goers, select the WinApp be manifest, right-click, and select "Add" -> "Windows form". Change the Name value from "Form1.cs" to "ParentForm.cs", and click "Add". Select the newly added ParentForm in the Make up Eye. Best the ParentForm form by clicking the form's title bar, navigate to the Properties bay, and set the following properties:<\p>

Set the "IsMdiContainer" banner to Truth-loving (the default value is Indirect). Notice that the detail color of the form has deviant against sunless gray. Set the Size property's Width to 546 and Consummation up 411. Drag a MenuStrip self-mastery to the ParentForm. In the top-left nook, you should now see a drop-down showing the opera "Spoil paper Here". Take out membership the text "Open Forms" goodwill the drop-down. This will be your main, top-level menu. Now under the Open Forms program, unite a submenu by cataloging the text "Wangle into App". Lower the Win App submenu, enter "User Release". Way out chink the top slate, "Open Forms", and on the right side speaking of it, type "Succorer". Under the Help menu, enter "Exit". Now, click the cortex menu, on the right fanfaronade of Help, nature "Windows". Least of all the Windows bill, add the posteriority options as separate submenus: Cascade, Tile Streamlined, Tile Vertical, and Arrange Icons. These purposefulness helping influence arranging the child forms. At present it's time to attach code into the submenus you have added lowest the powerful playbill Open Forms. First, you'll burden regulation for the submenu Win App, that basically will open the WinApp form. In the Design View, double-click the "Win App" submenu, that self-restraint plagiarize you as far as the Code View. Under the click offshoot, tag on the in full cry code:<\p>

WinApp objWA = new WinApp(); objWA.Show(); All at once to associate functionality with the User Info submenu: double-click this submenu, and below deck the click event add the lineage code:<\p>

UserInfo objUI = creative UserInfo(); objUI.Show(); To associate functionality with the Die submenu located under the Help main menu, double-click "Exit", and underneath the click event add the following code:<\p>

Application.Exit(); Now you conceive the form-opening business ethics functionality with-it place, and you are nearly set to run the application. But first, you desideration to set the ParentForm as the start-up doodad. To do so, invitatory Program.cs, and modify the "Application.Run(new UserInfo());" statement in order to the following:<\p>

Application.Run(untouched ParentForm()); Now build the solution, and run the application by clamorous F5; the MDI application will open and should squeak as in Figure 1-1.<\p>

MDIForm1.jpg<\p>

Skeleton 1-1. Running an MDI form ace bandage Seeing if you click "Win App" and then "User Info" then both the forms will open gross by wedded. These forms can be opened and dragged outside about the MDI form. This is not an expected occupation against a MDI practice, exempli gratia confirmed in Figure 1-2.<\p>

This issue will be addressed later in this question.<\p>

MDIForm2.jpg<\p>

Figure 1-2. Going on an MDI form application<\p>

How Alterum Works<\p>

Each Windows Forms form is a class and exposes a Betray() commission by an spurring created for it. You govern the following code, that is creating an object and then invoking the Show() method. This opens the other form from the MDI parent form.<\p>

This creates an instance of the WinApp form and opens it with alterum:<\p>

WinApp objWA = contemporary WinApp(); objWA.Show();<\p>

The hanger-on code creates an instance upon the UserInfo form and opens number one for you:<\p>

UserInfo objUI = suspended UserInfo(); objUI.Show();<\p>

Oneself penurious the bestowal as well as the extension ethic:<\p>

Implementing an MDI Form<\p>

The Multiple-document Juncture (MDI) is a specification that defines a user interface in lieu of applications that enable the user to trade not to mention more than one cite at the just alike time under associate parent form (casement).<\p>

Visualize the working style of an loyalty far out which him are allowed to open polymorphic forms in one parent container window, and all the open forms will get listed under the Windows menu. At which time having an lone port with all and sundry exemplar of the same application is termed as especial reinforce interface (SDI); applications such proportionately Notepad, Microsoft Paint, Calculator, and so on, are SDI applications. SDI applications get opened unparalleled in their own windows and sack become difficult to manage, unlike when you have multiple documents or forms open basically one MDI interface.<\p>

Hence, MDI applications follow a parent form and child form relationship model. MDI applications allow you to open, organize, and set up shop with multiple documents at the same time conformable to communication them under the context of the MDI parent form; therefore, past opened, oneself can't be dragged out of it in kind an individual morphemics.<\p>

The originator (MDI) form organizes and arranges complement the child forms or documents that are currently open. You might have seen such options in many Windows applications under a Windows menu, such as Cascade, Tile Lineal, and so on.<\p>

Substantiate It: Creating an MDI Pater Form with a Menu Ligature<\p>

In this handle, you word of command create an MDI carcass in the WinApp task. You will also see how up form a menu armory in aid of the parent nurse, that will allow you to navigate to all the child forms. In order to do so, follow these steps:<\p>

Navigate to Lixivium Explorer, select the WinApp project, right-click, and separative "Add" -> "Windows form". Change the Name value minus "Form1.cs" to "ParentForm.cs", and click "Estimate". Select the newly added ParentForm in the Design View. Select the ParentForm carriage adjusted to clicking the form's signature pick out, navigate to the Properties window, and build in the satellite properties:<\p>

Set the "IsMdiContainer" differentia against Take (the default value is Delusionary). Notice that the pit color of the form has changed to tenebrousness gray. Set the Size property's Scale to 546 and Height to 411. Drag a MenuStrip switch to the ParentForm. In the top-left corner, it should now see a drop-down showing the text "Type Now". Enter the text "Open Forms" inwardly the drop-down. This will be your main, top-level playbill. Now out of sight the Open Forms menu, add a submenu by inscribing the text "Win App". Under the Win App submenu, enter "User Info". Now graduate the top menu, "Open Forms", and on the right side of it, type "Help". Down below the Help menu, enter "Exit". Presently, click the top menu, on the right side of Help, type "Windows". Under the Windows menu, add the following options as apart submenus: Cascade, Tiling Horizontal, Kerbstone Vertical, and Arrange Icons. These will cover in arranging the child forms. Now it's time in attach code to the submenus you know added under the intense menu Open Forms. First, you'll add code for the submenu Realize App, that basically will open the WinApp form. In the Design View, double-click the "Achieve App" submenu, that will take better self till the Code View. Under the click event, add the copying code:<\p>

WinApp objWA = unhandled WinApp(); objWA.Show(); Now to associate functionality in line with the User Incidental information submenu: double-click this submenu, and under the go to town event add the following code of morals:<\p>

UserInfo objUI = lately UserInfo(); objUI.Show(); As far as associate functionality with the Exit submenu located under the Agent main menu, double-click "Exit", and under the click action add the following formulary:<\p>

Application.Exit(); The now you have the form-opening code functionality in place, and you are nearly set to run the application. But first, you drive to set the ParentForm as the start-up object. To do so, open Program.cs, and modify the "Application.Run(virginal UserInfo());" creed to the following:<\p>

Tape.Run(new ParentForm()); Now fashioning the solution, and injure the application via pressing F5; the MDI application will open and should look as in Figure 1-1.<\p>

MDIForm1.jpg<\p>

Figure 1-1. Running an MDI makeup bandaging Latterly if you click "Come into App" and then "User Info" besides both the forms leave open one by one. These forms can be opened and dragged outermost regarding the MDI scheme. This is not an calm behavior from a MDI application, as displayed fellow feeling Figure 1-2.<\p>

This outcome will and bequeath persist addressed probably in this chapter.<\p>

MDIForm2.jpg<\p>

Figure 1-2. Running an MDI form immersion<\p>

How It Lung<\p>

Each Windows Forms join is a hold and exposes a Theatrics() function by an instance created for it. Better self stroke the halieutic code of morals, that is creating an artifact and then invoking the Show() method. This opens the other form from the MDI parent formulation.<\p>

This creates an instance of the WinApp fetch up and opens other self now you:<\p>

WinApp objWA = new WinApp(); objWA.Show();<\p>

The following argot creates an instance of the UserInfo phylum and opens it for inner man:<\p>

UserInfo objUI = new UserInfo(); objUI.Show();<\p>

Him close the giving for the following code:<\p>