G
Guest
There seems to be a problem with opening a MDI child form with the initial
WindowState set to Maximized when the MDI parent has a menu. This is a new
problem in .Net 2.0. The same code worked correctly in .Net 1.1.
The window is painted in the non-maximized state but the form acts as if it
is maximized. The child is displayed in the top left of the parents client
area and the child cannot be moved. Furthermore, the minimize, restore, and
close buttons are displayed in the parent frame.
I have been able to reproduce this in a very simple application. It contains
a MDI parent with a menu and a MDI child with nothing on it. The only code in
the project (other than the generated code) is in the parent to launch the
MDI child in the maximized state. I will make the sample project available
upon request (just let me know the email address to send it to).
WindowState set to Maximized when the MDI parent has a menu. This is a new
problem in .Net 2.0. The same code worked correctly in .Net 1.1.
The window is painted in the non-maximized state but the form acts as if it
is maximized. The child is displayed in the top left of the parents client
area and the child cannot be moved. Furthermore, the minimize, restore, and
close buttons are displayed in the parent frame.
I have been able to reproduce this in a very simple application. It contains
a MDI parent with a menu and a MDI child with nothing on it. The only code in
the project (other than the generated code) is in the parent to launch the
MDI child in the maximized state. I will make the sample project available
upon request (just let me know the email address to send it to).