Tim Steenwyk

The following seemed to help the performance issue in our application. Your mileage may vary, of course: ``` dockPanel.SuspendLayout(true); dockPanel.DockWindows[DockState.DockLeft].SuspendLayout(); dockPanel.DockWindows[DockState.DockRight].SuspendLayout(); dockPanel.DockWindows[DockState.DockTop].SuspendLayout(); dockPanel.DockWindows[DockState.DockBottom].SuspendLayout(); dockPanel.DockWindows[DockState.Document].SuspendLayout(); // call LoadFromXml dockPanel.DockWindows[DockState.Document].ResumeLayout(true); dockPanel.DockWindows[DockState.DockBottom].ResumeLayout(true); dockPanel.DockWindows[DockState.DockTop].ResumeLayout(true);...

See `DockPanel.DockLeftPortion` (and `DockRightPortion`, `DockTopPortion`, `DockBottomPortion`). I'm fairly certain those properties set the default portions for the docked tools (which I think is what you are trying to do).

Can you put the form you don't control inside a wrapper-form that does inherit from DockContent (**Controls.Add(otherForm)**)? That is basically how DockContent gets embedded into the DockPanel.

Sorry, I completely forgot about this. I doubt it is intentional, and it probably just happened to be that way. It's possible it has something to do with the way...