We are not sure we understand what the issue you are experiencing exactly is.
By design the RadDocking control's save/load layout funtionality saves and loads the current state
of any RadPane, RadPaneGroup and RadSplitContainer instance. The funtionality saves only layout specific properties if no SerializationTag
is set to the element instance. This is done in order to generate a light weight
layout XML. In most scenarios it is important to set the RadDocking.SerializationTag
on any RadPane, RadPaneGroup or RadSplitContainer which contains important properties which should be saved in the layout.
In all of our tests the Width and Height properties of any RadSplitContainer are correctly saved and loaded. The SplitterChange
property is an internal property of our ProportionalStackPanel which is used to maintain the size differences between the parts of the RadDocking control.
Could you describe to us in more details the specific scenario where the Width and Height properties of an RadSplitContainer instance is not persistence by save/load layout functionality?
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.