MDI Forms
Uploaded by
ScribdTranslationsMDI Forms
Uploaded by
ScribdTranslationsTASK N° 3.
1
UNIVERSITY OF THE ARMED FORCES “ESPE”
COMPUTER TECHNOLOGY CAREER
NRC: 3038
TEACHER: Eng. Doris Chicaiza
DATE:
MEMBERS: García Stalin, Iles Paola, Esthela Tenorio
LEVEL: Fifth semester
1. ISSUE:
MDI Form
Properties, methods and events
2. GOALS
General objective
Investigate the development of MDI forms with their respective properties,
methods and events today through research.
Specific objectives
Understand the MDI Forms commands, taking into account their functions and
properties.
Apply the methods used in the Visual Studio platform in order to understand
how the commands work.
Develop programs with user interfaces on the Visual Studio platform applying
MDI Forms
3. DEVELOPMENT
MDI stands for Multiple Document Interface in English and Multiple Document
Interface in Spanish and is used to display several forms from a main Form.
The counterpart of the MDI is the SDI, which is a Single Document Interface, that
is, when the project is a single form or interface.
In an MDI there is a main form or Parent form that will contain the secondary forms
or child forms.[1]
MDI applications typically consist of a main window, which may contain other
interior windows. Each document that is opened appears in an interior window. [2]
An MDI application has two basic elements:
An internal JDesktopPane panel, which will contain the internal windows.
A class of type JInternalFrame, which will define the layout of the internal
windows.
The JInternalFrame class that we add will have the name that we want to assign to it
and will serve as a template to create the internal windows of our project. This class
may have internal methods to access the elements of the internal windows.
From the main window, objects of the internal window class will be created, and
options will be defined regarding the possibility of maximizing, closing,
minimizing, etc., said windows.
From the main window, the methods programmed in the internal window will be
used to be able to handle it easily.[3]
A project can only contain one MDI form, but all necessary secondary MDI forms.
An MDI form is called a parent and its children are called Children.
Parent MDI form : It is the container for the secondary forms. An application can
only have one MDI form. They can only contain Toolbar, Statusbar and PictureBox
controls. It is not possible to place another control on the MDI form.
MDI child forms: Every child form is located within the parent MDI. When a child
window is minimized, its icon appears in the parent window and not on the taskbar.
When a child window is maximized, it occupies the entire internal area of the parent
form.
Disadvantage:
The main disadvantage of MDI is the paucity of information about open windows:
To view a list of open windows of an MDI application, the user usually has to select
a specific menu ("window list" or something similar), if this option is available.
With an SDI application, the window manager taskbar displays the currently open
windows. In recent years, applications have added taskbars or tab systems to MDI
applications, making this criticism obsolete. Some people use a different name for
this type of interface, "tab interface" (TDI). When using tabs to control windows,
they typically cannot be resized separately.[4]
Values that can be obtained
The download_mode argument returns the following values:
4. CONCLUSIONS
MDI (multiple document interface) applications allow you to display multiple
documents at the same time, each in its own window. MDI applications typically
have a Window menu item with submenus that allow you to switch between
windows or documents.
MDI programming consists of creating applications capable of opening several files
and displaying them in different internal windows, allowing several documents to be
displayed at the same time, each of them in its own window. Which usually have a
window menu item with submenus that allows you to change.
When a child MDI form has a MainMenu component (typically with a menu
structure with menu items) and is opened within a parent MDI form that has a
MainMenu component (typically with a menu structure with menu items) menu),
menu items are automatically merged if you have set the MergeType property (and,
optionally, the MergeOrder property).
5. RECOMMENDATIONS
It is advisable to take into account the different types of data that need to be used
and their respective characteristics to make good use of them.
Investigate in more depth the different topics proposed to answer the different
doubts that arise during the course of the investigation.
Carry out exercises to reinforce each topic investigated and put what you have
learned into practice.
6. BIBLIOGRAPHIES
ADDIN ZOTERO_BIBL {"uncited":[],"omitted":[],"custom":[]} CSL_BIBLIOGRAPHY [1]
«Formularios MDI - Visual Basic paso a paso». [En línea]. Disponible en:
https://www.aulafacil.com/cursos/programacion/visual-basic-paso-a-paso/formularios-
mdi-l42176. [Accedido: 07-ene-2020].
[2] «1.4. Formularios MDI y SDI.» [En línea]. Disponible en:
https://virtual.itca.edu.sv/Mediadores/dacs2013/14_formularios_mdi_y_sdi.html.
[Accedido: 07-ene-2020].
[3] E. Reyes, «INFORME FORMULARIOS MDI».
[4] Lic. Rolando Torres, «Formulario mdi», 02:54:46 UTC.
