setting windowstate

[vbgladiator]

Hey,

I have a form that opens up another form. In the newly opened form I have the following code running to maximize it:

Me.WindowState = FormWindowState.Maximized

When I close the newly opened form, the previous form that opened the one being closed is maximized as well. Why is that happening?

[gigemboy]

Do you have some kind of maximize code anywhere inside of the one that originally called it?

[vbgladiator]

no, only the form that is opening up has that code.
It's a form showing a report so I want it maximized by default.
That is the only place in the app that has maximizing code in it.

[conipto]

What event is that code inside? It's definately not inside the first form, even during the showing of the second? Me. anything refers to the current object.

Bill

[vbgladiator]

The code is inside the form that is opening up. Yes, it does uses the me object to maximize itself.

[jmcilhinney]

I'd suggest that you create an empty Resize event handler for the first form and put a breakpoint on the declaration. That way you can look at the call stack when the resizing happens and see where it came from.

[vbgladiator]

In the report form (the one that was maximized), the following line causes the calling form to maximize as well

MyBase.Dispose(disposing)

it happens in teh Dispose sub.

This is weird.

[jmcilhinney]

Have you derived this "report form" from another form of your own creation, or does it inherit Form directly?

[vbgladiator]

Inherits System.Windows.Forms.Form

[jmcilhinney]

When your breakpoint gets hit can you double-click on the entries in the call stack to look at that code, or is it not accessible?

[jmcilhinney]

You haven't at any point set the second form as the Owner of the first have you?

[vbgladiator]

no, the mdi parent form is the parent of the new form, as it is the parent for all the other forms.

[maged]

i think this is the standard behaviour for mdi Forms.

all mdi childs tends to have the same window state, i dont like it either but that is the way it is

rgds

[jmcilhinney]

OK, nowhere previously did you mention that any of this involved MDI forms. I assumed that it was just one top-level form opening another top-level form. Now that we know that it's MDI, do you mean that the parent is maximised when the child is or that another child is maximised? If it's the latter then, as maged says, that is normal behaviour. It is not possible to chnage that without using extremely hacky means, and even then I'm not sure that there aren't issues.

[vbgladiator]

no, the parent is maximized at all times. The form that is calling the report form gets maximized after I exit the report form. The report form maximizes itself upon the Form_Load event.

[jmcilhinney]

If one MDI child is maximised then they all are. That's standard behaviour. Try switching to the first child window before closing the second and you'll see that it is already maximised at that point. perhaps it doesn't technically happen until the first time you view it but as soon as you maximise one child then they will all be maximised the next time you look them. The way to workaround this may be to set the WindowState of the second window back to Normal before closing it.

[vbgladiator]

Yeah, I though about doing that. My app is becoming quite large and I don't want to be going through all the forms that might possibly be calling the report form and trapping their resize event. Damn...

[conipto]

How about just calling this in the form.closing event of your report form:

Me.WindowState = FormWindowState.Normal

Bill