我继承了从previous开发者，我现在的工作一个应用程序框架。这个框架利用多个父/子关系。在许多情况下，父/母/子发生。我问他为什么没有使用MDI和他说，几年前，当他开始，MDI了关于previously表示关系方案的主要缺陷。尤其是与多个家长。

I have inherited a application framework from the previous developer where I now work. This framework utilizes multiple parent/child relationships. In many instances parent/parent/child occur. I asked why he WASN'T using MDI and he stated that years ago, when he had started, MDI had major shortcomings concerning the previously stated relationship scenarios. Particularly with the multiple Parents.

我的实际问题是; MDI是否仍然有这些缺点？ ＆放大器;你们当中谁曾与MDI的工作，你有什么问题，你是怎么克服的？

My actual questions are; Does MDI still have these shortcomings? & Those of you who have worked with MDI, what problems did you have and how did you overcome them?

感谢您！

推荐答案

与MDI接口的一个问题是，你不能你MDI容器内登记无限窗口的呢（见的此Microsoft知识库项）。以为我发帖说，因为我看到很多MDI应用程序打的错误时，其大量使用。

One problem with MDI interfaces is that you can't register unlimited Window's within your MDI Containers anyway (see This Microsoft KB item). Thought i posted that up because i've seen many MDI applications hit that error when its heavily used.

我一般喜欢SDI接口，并使其在产卵的新窗口的'东西'每个实例的'东西'的多个实例，而不是共享相同的控件和窗口。

I generally like an SDI Interface and make it share the same controls and windows over multiple instances of 'something' instead of spawning a new Window for each instance of 'something'.

我不知道程序界面的细节，但我还没有找到的东西，不可能是修改，以SDI接口和一些模式对话框（如果确实需要）。

I dont know the specifics of the programs interface but i've yet to find something that couldnt be reworked to an SDI interface and some modal dialogs (if really needed).