ID Number: Q81956
1.00
WINDOWS
Summary:
When an MDI Child custom control is placed on a form, no other non-MDI
Child control(s) should be placed on the same form. If a non-MDI Child
control is placed directly on the parent form, the MDI child window
may appear to adopt, or "pick up," the control when the MDI child
window is minimized then maximized (so that it covers the control on
the form once maximized or sized).
This information applies to Microsoft Professional Toolkit for
Microsoft Visual Basic programming system version 1.0 for Windows.
More Information:
Steps to Reproduce Behavior
---------------------------
1. Run Visual Basic, or from the File menu, choose New Project (ALT,
F, N) if Visual Basic is already running. Form1 is created by
default.
2. From the File menu, choose Add File. In the Files box, select the
MDICHILD.VBX custom control file. The MDI Child tool appears in the
toolbox.
3. Place an MDI Child control on Form1.
4. Place another control (for example, a command button) directly on
the form outside the MDI child window.
5. Press F5 to run the application.
6. Move the MDI child window so that it is covering the command button
by clicking and dragging the title bar.
7. Click the Minimize button (the down arrow) on the MDI child window
to minimize it.
8. Double-click on the icon of the minimized MDI child window to
restore it.
9. The MDI child window will now appear to have a command button on
it.
The MDI child window does not actually have a fully functional copy of
the control that was placed directly on the form--it has only an image
of the control (in this example, a command button).
When using the MDI Child custom control, you should only place
controls directly on the child windows you create. The "Microsoft
Visual Basic Custom Control Reference" states on page 184 that no
controls should be placed on the form (parent window) when using MDI
child windows.
Additional reference words: 1.00