By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,948 Members | 1,692 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,948 IT Pros & Developers. It's quick & easy.

Mdi Child behavior

P: n/a
In my Mdi Application, I load a default child form at startup using
WindowState = Maximized.

If I open another child form, it is also Maximized. When the child form
maximizes, it looks like all of the active child forms (all 2 of them) go
through a series of changes from WindowState Normal back to Maximized. It
does it quickly (say 400 ms), but it is noticable and it irritates me (since
I designed it, and did not intend for this to happen).

After testing with the second child window, I exit it.

So far, so good (other than the annoying flicker that I can't figure out).

Today, I went to open the second child window again (I forgot to test a
feature). After it was called, both windows took on a Cascade looking effect.
Instead of clicking the Maximize button, I tried to resize the window I
wanted to use, and that was when I noticed the child forms will not resize.

I created a second test Mdi Application, but it behaves normally (it allows
resizing and there is no noticable flicker when going from one form to
another).

Does anyone have a clue what I could have done to cause this? The
application I have built that uses this is quite large, so just posting the
code would take some time. If I knew the relivant code, I'm sure it would be
smaller, but then I would know what area to play around with.

I am open to any ideas.
Oct 28 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.