MDI child window state and icon problems -- dotnet windows forms

Alex Broide
10/12/2006 7:00:01 PM

I'm developing a MDI application in VB.NET 05
First probelm.
When MDI child is shown it should appear maximised. If i set WindowState for
MDI child after it is created but before it is opened, it doesn't appear
maximised when it is shown. The only workaround i found is to set WindowState
in Load event. Is this the correct behaviour or bug? Is what i'm doing
correct or is there a better way?

Second problem.
I have set an icon for the MDI child form. When the form is first shown in
maximized state a default icon is displayed in the menu strip and not the one
i assigned to the form. If i restore the form the correct icon is displayed.
If i maximize the form again the correct icon is shown in the menu strip. So
basically the problem is that if MDI child shown in maximised state the
default icon is displayed and not the correct one.

Thanks

MobileMan
10/15/2006 7:55:02 AM

First Problem .............

This is correct. Use the Load event handler for this type of functionality.

Second Problem ........

Don't have an answer for this one but you might find it interesting that we
use Vs05 also and experience the same behavior in C#.
--
Stay Mobile

[quoted text, click to view]

Alex Broide
10/15/2006 5:07:01 PM

Hi MobileMan

Thanks for your input.
Hopefully someone else knows about the second problem.

Alex

[quoted text, click to view]

Garry
10/25/2006 12:46:37 PM

Somehow I am getting the impression that vb.net was not really designed to
accomodate MDI applications however much Microsoft drums on about
WindowsForms. It looks as if it was added as an afterthought. Add a
ClientRectangle which mysteriously appears when MDI property is true.

Then, hide any serious HELP topics so that the user may give up..

Makes you wonder what they were really thinking about when sitting down and
designing the .NET family. Internet. Internet. and more Internet.

But some applications are just not Internet and will not be until the
internet is almost instantatenous and security concerns have been beefed up
to a point where the user is no longer concerned by them

I would be happy to continue with VB6 but the maintenence will not be
forever.

It is very slack now.

Garry

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet windows forms

dotnet windows forms : MDI child window state and icon problems