MDI Application development question...

[SpotNet]

Hi NewsGroup,

Currently constructing a MDI application with tree view functionality. That
is to say my application will look something like Windows Explorer with the
ability to view data and graphs in separate MDI child windows depending on
the options chosen. I have a MDI child window with the tree view control on
one side and listview, custom input screen controls on the other side
separated by a splitter control, which become visible (or not) depending on
the nodes selected on the tree view.

My question comes in light of many posts I've read in the past stating
*never* put controls on the MDI Parent window even if you can. I have
thought of placing the tree view, splitter and associated view controls on
the MDI Parent but have not due to these previous posts. Never been
*really* told or know why, can some one out there tell me why one should not
place controls on the MDI Parent window for an application as such? Even if
it is a matter of development practice not to, what are the issues involved
in doing so?

Many thanks and regards,
SpotNet

PS. I am constructing this in C# which is the reason I posted here, I know
it's a bit more general than that. Cheers ;~)

 

[Nicholas Paldino [.NET/C# MVP]]

SpotNet,

The only reason I can think of is because there might be some
interaction with the parent control and the child controls that is a little
funky. Can you show the articles/postings you are referring to?

Also, what you are doing sounds very much like something that one would
use Microsoft Management Console for. Is this an application that would be
better of hosted there? If so, you could cut out a lot of your coding by
letting MMC do most of the UI for you.

Hope this helps.

 

[SpotNet]

Thanks Nicholas,

Articles I read which were mainly from the VB 6 days. I can understand why
you would not place a dropdown or a text box control on an MDI, but when it
comes to tree view structured application, I found it makes more sense to
place a tree view control on the MDI with associated view controls. It's
made communicating between these controls a whole lot more easier. Thanks
again Nicholas.

Regards,
SpotNet.

SpotNet,

The only reason I can think of is because there might be some
interaction with the parent control and the child controls that is a
little funky. Can you show the articles/postings you are referring to?

Also, what you are doing sounds very much like something that one would
use Microsoft Management Console for. Is this an application that would
be better of hosted there? If so, you could cut out a lot of your coding
by letting MMC do most of the UI for you.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Hi NewsGroup,

Currently constructing a MDI application with tree view functionality.
That is to say my application will look something like Windows Explorer
with the ability to view data and graphs in separate MDI child windows
depending on the options chosen. I have a MDI child window with the tree
view control on one side and listview, custom input screen controls on
the other side separated by a splitter control, which become visible (or
not) depending on the nodes selected on the tree view.

My question comes in light of many posts I've read in the past stating
*never* put controls on the MDI Parent window even if you can. I have
thought of placing the tree view, splitter and associated view controls
on the MDI Parent but have not due to these previous posts. Never been
*really* told or know why, can some one out there tell me why one should
not place controls on the MDI Parent window for an application as such?
Even if it is a matter of development practice not to, what are the
issues involved in doing so?

Many thanks and regards,
SpotNet

PS. I am constructing this in C# which is the reason I posted here, I
know it's a bit more general than that. Cheers ;~)