MDI child maximizing doesn't work correctly

[Elmo Watson]

(using VS.net 2005 - never used DotNet WinForms til now - previously only
used VB6)

I have set my mdi child form to a window state of maximized.

However, the first file I open is not maximized and I can not get to the
drag bar.

But then, the second file I open (using the same function) IS maximized and
it maximizes the first, previously opened mdiChild also...

What's the trick here, that I assume I'm missing?

 

[Herfried K. Wagner [MVP]]

I have set my mdi child form to a window state of maximized.

However, the first file I open is not maximized and I can not get to the
drag bar.

But then, the second file I open (using the same function) IS maximized
and it maximizes the first, previously opened mdiChild also...

How are you opening the child forms?

It's by design that maximizing one of the child forms will maximize all
other MDI children too.

 

[Elmo Watson]

I have a method in a Module, in order to simplify things
objDoc=New frmEdit
objDoc.MdiParent=frmMain (keep in mind, this is in a module)
objDoc.Text="Untitled"
objDoc.Show

I'm totally open to any new knowledge on how to do this - I'm very new at
DotNet WindowsForms - I was a VB6 guy for years and now, I'm starting with
v2.0 of DotNet

 

[Herfried K. Wagner [MVP]]

I have a method in a Module, in order to simplify things
objDoc=New frmEdit
objDoc.MdiParent=frmMain (keep in mind, this is in a module)
objDoc.Text="Untitled"
objDoc.Show

I'm totally open to any new knowledge on how to do this - I'm very new at
DotNet WindowsForms - I was a VB6 guy for years and now, I'm starting with
v2.0 of DotNet

Are you sure you set the MDI child's 'WindowState' to 'Maximized'?

 

[Elmo Watson]

Absolutely - I've checked it several times.

Are you sure you set the MDI child's 'WindowState' to 'Maximized'?

 

[Elmo Watson]

Anyone have a fix for this?

Absolutely - I've checked it several times.

 

[Guest]

I didn't have this problem with the VS 2005 beta, including a project that
was started in beta and has now been updated to the final release. But in new
projects started in the release version I have this problem.

The closest I have come to finding a fix is to set window state in the load
event of the child form.

Geoff

 

[Martin]

Glad to hear I'm not the only one who has this problem...
I stumbled on the same "fix" as you did.