Hello JOSE MANUEL PÉREZ RAMÍREZ,
Thank you for the question.
The API for using RadDock in MDI scenario is pretty much the same as using the old DockingManager in MDI scenario. You should simply set the AutoDetectChildForm
to true and RadDock will automatically host the MDI children.
Having a HostWindow with a child form in the ToolWindows, but not in the DocumentWindows is actually a result of a feature. When a HostWindow is created to host a child form, this HostWindow has a DockType ToolWindow
. This allows you to float the document containing the child form and even you can dock it in a ToolTabStrip with other ToolWindows. If the DockType
, you will not be able to perform these operations.
However, I agree that some of you, our users, may want to have the default DockType
of a HostWindow in MDI scenario set to DocumentWindow
. Therefore, in Q2 2009 SP1 we will make the DocumentWindow
the default DockType
and we will introduce a property which will switch between DocumentWindow
types for a HostWindow containing a child form.
As to the form closing issue, you are correct. When a child form is closed, the HostWindow that contains the form is not closed automatically. This issue will be addressed in Q2 2009 SP1 as well. For the time being you can subscribe to the FormClosed event of the form and close the parent HostWindow:
|void form_FormClosed(object sender, FormClosedEventArgs e)
Thank you for sharing your feedback with us. I am updating your Telerik points. If you have additional questions, feel free to contact me.
All the best,
the Telerik team