MdiClient

[John F]

Is there a way to place controls on the surface of MdiClient and have it
always stay in the background when new child forms are loaded into the MDI?
When I place controls on the surface of an MDI app and load child forms, the
controls place on the surface poke through the child form.

In the MDI paradigm, is it not wise/proper to use the MdiClient as a
controls surface?

--
Thanks, John F

[Stoitcho Goutsev \(100\)]

John,

The answer is NO.

When you set up a form to be a MDI container the frame work creates a
control of type MDIClinet (undocumented class meant to be used internaly
according to MSDN) that hosts all MDI children.

All other controls that you add to the form will be siblings of this control
wither over the MDIClient and all its children (MDI child forms) or under
(if it is possible to move it there) the MDIClient, thus covered and
invisible.

The only way if it was possible( but it is not) was if you could add that
control as a child of the MDIClient control, but the MDIClient control
checks all the controls added to the Controls collection to be MDI child
forms and throws exception otherwise.
--
HTH
Stoitcho Goutsev (100)

"John F" <[e-mail]> wrote in message
news:28******** *************** ***********@mic rosoft.com...

Is there a way to place controls on the surface of MdiClient and have it
always stay in the background when new child forms are loaded into the
MDI?
When I place controls on the surface of an MDI app and load child forms,
the
controls place on the surface poke through the child form.

In the MDI paradigm, is it not wise/proper to use the MdiClient as a
controls surface?

--
Thanks, John F