mdi form always starts maximised

  • Thread starter Thread starter androoo
  • Start date Start date
A

androoo

How can i avoid this ? i tried setting the size properties but the
damn thing completely ignores it..
anyone know how ?

cheers

andy
 
Check the WindowState property and make sure it is not set to maximized.

Charlie
 
How can i avoid this ? i tried setting the size properties but the
damn thing completely ignores it..
anyone know how ?

cheers

andy
Click to expand...

For your form_load event:
<form>.WindowState = vbNormal

may help you.
 
How can i avoid this ? i tried setting the size properties but the
damn thing completely ignores it..
anyone know how ?

cheers

andy
Click to expand...

Or <form>.WindowState = FormWindowState.Normal
 
Yes have that already and also set size width and height but still the
form goes max...any ideas how to force it?

Me.WindowState = vbNormal
Me.Width = 858
Me.Height = 656
 
Yes have that already and also set size width and height but still the
form goes max...any ideas how to force it?

   Me.WindowState = vbNormal
   Me.Width = 858
   Me.Height = 656
Click to expand...

You should have forced it if you put WindowState propety on your
form's load event. If you still see your form maximized then your
screen resolution might be close or same with your form's size which
is not an actual maximization.
 
its strange its not to do with resolution--
very annoying but if no one else gets this then it must be a setting
somewhere or piece of code upsetting things..
 
I'm experiencing a problem that's similar; I start my MDI application. When
loading the main MDI form, I show the first child form form and set it to
maximize. The windowstate setting of that first MdiChild form seems to be
causing another form that shares the same MdiParent form (but is otherwise
independent) to also be maximized when I show it as well. I see no way the
windowstate properties of these 2 forms can be related using any of the code
I've written.
 
Try to set the code right before your 'show' command.

I once had this issue, and it seemed to ignroe the properties from the
designer, and I had to do it during runtime.
 
Yeah, the behavior I described is what occurs when I set it at runtime; it
occus whether I set the WindowState before or after Show().

I'm getting some other unexpected behavior using the form, so I'm thinking
that there are some conflicting properties upon loading or that something is
off in the designer code of the Window.
 
Back
Top