not an mdi child and parent at the same time - why?

[Bernie Yaeger]

A form may not be both a child window and an mdi parent, but why not? I can
think of many instances where such would be valuable. Indeed, the basic
structure of menus and submenus is the perfect metaphor for this.

Anyone know why this is so and/or if it can be overridden?

Thanks for any help.

Bernie Yaeger

 

[Herfried K. Wagner [MVP]]

A form may not be both a child window and an mdi parent, but why not? I
can think of many instances where such would be valuable. Indeed, the
basic structure of menus and submenus is the perfect metaphor for this.

MDI is informally "deprecated", because practice has shown that users have
problems to use MDI environments.

 

[Samuel R. Neff]

Where does it say MDI is informally deprecated? Sure Office is
leaning towars sdi but a lot of apps, including VS.NET,are still MDI,
and office supports both mdi and sdi.

I personally prefer the tabbed mdi instead of traditional MDI (which
is easily accomplished with Infragistics mdi manager) but still think
MDI is a good way to go when it's appropriate for the program.

It also should be easy enough to give the user the option whether to
make an app mdi or not.. just a matter of adding it to an mdi parent
or not... right?

Sam

 

[Herfried K. Wagner [MVP]]

Where does it say MDI is informally deprecated? Sure Office is
leaning towars sdi but a lot of apps, including VS.NET,are still MDI,
and office supports both mdi and sdi.

ACK, but classic MDI is not the default any more. It's replaced by tabbed
MDI.