Widget Header + Prism Region + Floating Window

2 posts, 0 answers
  1. Johannes
    Johannes avatar
    3 posts
    Member since:
    Apr 2014

    Posted 08 Jun 2015 Link to this post

    Hi Telerik Team,

     We have a several Widgets in Docking Control. Most Widgets have a PRISM Region in their Titlebar, this works good at the moment.

     But when Widgets get floated into the ToolWindow and then readded to the Docking I get exceptions from Prism etc.

     

    So I wanted to ask how do implement A Region inside Widget Title Bar Header that support Floating and readding to the Docking.

     

    Thank you

    Johannes

  2. Vladi
    Admin
    Vladi avatar
    744 posts

    Posted 11 Jun 2015 Link to this post

    Hi Johannes,

    Thank you for contacting us.

    Such issue could be observed if a region is set to a RadPaneGroup instance. In the RadDocking control in order to achieve flawless floating and docking of any of the control's RadPane instances the following mechanism is implemented:
    • When a docked RadPane is being floated it is removed from its RadPaneGroup. This is where the connection with the region could be lost if a PaneGroup is set as a region.
    • A new RadPaneGroup is created by the control's GeneratedItemsFactory.
    • The floated RadPane is added to that new group.
    • A new RadSplitContainer is created and the new group is added to it.
    • A new ToolWindow instance is created and the new split container is added to it.
    • Finally the window is added to the RadDocking control.

    In that process the old RadPaneGroup which is used as a region is lost as it is never moved and is left in docked state in the control.

    When using the RadDocking control with PRISM it is recommended to use the whole control as a region. This way the region will never be lost. You can take a look at our "ShellPrism" example from our GitHub repository which demonstrates this approach. Another approach could be to use the RadPane instance as a region and add a ContentControl inside its Content which will be further used by the PRISM library.

    Hope this is helpful. If we have missed something please let us know.


    Regards,
    Vladi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for WPF is Visual Studio 2017 Ready
Back to Top