SaveLayout problem

[Anthony Ortiz]

Hello,

I have been trying to save the layout of my RadDock project with partial success. The problem I'm having is with the "Chart Group" tab; after inspecting the saved layout I realize it doesn't save any of its children. I've taken the ChartGroup snippet and pasted it here. Attached is a screenshot of the ChartGroup (ChartGroup is one of three tabs).

Regards,

Anthony

<radDock:RadDocking x:Name="radDocking1" Grid.Row="1" Loaded="radDocking1_Loaded">
 ...

                <radDock:RadPane x:Name="uxChartGroup" Header="Chart Group" IsPinned="True" CanUserClose="False" CanUserPin="False" telerik:RadDocking.SerializationTag="ChartGroupPane">

                    <radDock:RadSplitContainer Orientation="Horizontal" >

                        <radDock:RadSplitContainer InitialPosition="DockedLeft" Orientation="Vertical">

                            <radDock:RadPaneGroup x:Name="uxMC">

                                <radDock:RadPane Title="Market Cap" TitleTemplate="{StaticResource TitleTemplate}" telerik:RadDocking.SerializationTag="MarketCapPane">

                                    <telerik:RadChart />

                                </radDock:RadPane>

                            </radDock:RadPaneGroup>

                            <radDock:RadPaneGroup x:Name="uxS">

                                <radDock:RadPane Title="Sector" TitleTemplate="{StaticResource TitleTemplate}" telerik:RadDocking.SerializationTag="SectorPane">

                                    <telerik:RadChart />

                                </radDock:RadPane>

                            </radDock:RadPaneGroup>

                        </radDock:RadSplitContainer>

                        <radDock:RadSplitContainer Orientation="Vertical">

                            <radDock:RadPaneGroup x:Name="uxV">

                                <radDock:RadPane Title="Volume Distribution Summary" TitleTemplate="{StaticResource TitleTemplate}" telerik:RadDocking.SerializationTag="VolumeDistributionSummaryPane">

                                    <telerik:RadChart />

                                </radDock:RadPane>

                            </radDock:RadPaneGroup>

                            <radDock:RadPaneGroup x:Name="uxD">

                                <radDock:RadPane Title="Volume Distribution Details" TitleTemplate="{StaticResource TitleTemplate}" telerik:RadDocking.SerializationTag="VolumeDistributionDetailsPane">

                                    <telerik:RadChart />

                                </radDock:RadPane>

                            </radDock:RadPaneGroup>

                        </radDock:RadSplitContainer>

                    </radDock:RadSplitContainer>

                </radDock:RadPane>
...

</radDock:RadDocking>

[Miroslav Nedyalkov]

Hi Anthony,

 Nesting SplitContainers and PaneGroups in RadPanes is not supported by the Docking control. This is the reason why your inner layout (inside the RadPane) is not serialized. The Docking control treats it as a normal content and doesn't understand that these are split containers, groups and panes so it doesn't serialize them.

Kind regards,
Miroslav Nedyalkov
the Telerik team

[Anthony Ortiz]

Hello,

Thanks for the quick reply. Since I have implemented this incorrectly, would you please post some pseudo-code that would work? I want the Chart tab (RadPane) to be a container that can contain other docking controls as you can see from the picture. I tried putting another RadDock in the Chart tab but this generated an error. Any suggestions would be appreciated.

Regards,

Anthony

[Miroslav Nedyalkov]

Hi Anthony,

 The Docking control doesn't support that functionality either. What I would suggest you is to host the Docking control into a TabControl (to replace the root-level PaneGroup and Docking with a TabControl). Hope this is acceptable for you.

All the best,
Miroslav Nedyalkov
the Telerik team

[Richard]

Do you intend on making nested Splitters serializable? We have the latest internal build. Is there plans to add this in the future? We have a situation where we would like to have three seperate panes inside of a pane group but to dispaly side by side without tabs.

Thanks

[Miroslav Nedyalkov]

Hi Richard,

 Could please explain us in more details what do you need to achieve? This way we may try to find out how to achieve it.

Kind regards,
Miroslav Nedyalkov
the Telerik team

[Richard]

Sure. We were trying to set up a few that has nested panes and splitters and have the rad doc save the layout

<

 

 

telerik:RadSplitContainer InitialPosition="DockedTop" Height="500">

 

 

 

 

    <telerik:RadPaneGroup x:Name="PnlMain" TabStripPlacement="Top">

 

 

 

 

        <telerik:RadPane x:Name="TrafficCalls" telerik:RadDocking.SerializationTag="TrafficCalls"

 

 

 

            IsPinned="True" Header="TrafficCalls" >

 

 

 

 

            <telerik:RadSplitContainer InitialPosition="DockedTop" Orientation="Horizontal">

 

 

 

 

                <telerik:RadPaneGroup>

 

 

 

 

                    <telerik:RadPane Header="Mobile Traffic" telerik:RadDocking.SerializationTag="TraffMob"/>

 

 

 

 

                </telerik:RadPaneGroup>

 

 

 

 

                <telerik:RadPaneGroup>

 

 

 

 

                    <telerik:RadPane Header="Traffic" telerik:RadDocking.SerializationTag="Traff"/>

 

 

 

 

                </telerik:RadPaneGroup>

 

 

 

 

                <telerik:RadPaneGroup>

 

 

 

 

                    <telerik:RadPane Header="Inbound Calls Handled" telerik:RadDocking.SerializationTag="inCalls"/>

 

 

 

 

                </telerik:RadPaneGroup>

 

 

 

 

           </telerik:RadSplitContainer>

 

 

 

 

    </telerik:RadPane>

 

 

</

 

 

telerik:RadPaneGroup>

 

 

 

 

 

 

 

 

 

 

 

 

</telerik:RadSplitContainer>

 

[Miroslav Nedyalkov]

Hello Richard,

 As we already said in this thread, this is not supported by the Docking control. What I need to know is what is the high-level goal of nesting SplitContainers into RadPanes? If we know the this we might be able to find out another way to achieve it.

Regards,
Miroslav Nedyalkov
the Telerik team