Hi,
I have an MDI application. Child forms have control boxes with
min/max/restore buttons. As well as using the MDIList menu property to
choose between forms, I have a representation of the forms that can also be
clicked on, with the intention of activating the relevant child form. This
second representation needs to keep in synch with the state of the MDI model
with respect to which form is active.
To this end, there is a function called SetActiveView that is called both
when the second representation is clicked and from an MDI child form's
Activate event. SetActiveView calls mdiParent->ActivateMdiChild(
newActiveForm ).
This is all fine except when the currently active form is Maximized. When
this is the case, using the MDIList menu items to select forms is all good,
and it de-maximizes the current active form. However, when SetActiveView is
called from my second representation, something goes wrong. The new form is
maximized, but the current active form leaves its control boxes at the top
of the parent window. This means that there are two sets of control boxes at
the top of the parent window, and one MDI child without any control boxes at
all.
Is this normal? Is there something else I should be calling to get 'proper'
MDI behaviour?
TIA,
Steve
