Invisible Floating Windows with Implicit Style

4 posts, 0 answers
  1. Aaron
    Aaron avatar
    2 posts
    Member since:
    May 2013

    Posted 12 Jan 2015 Link to this post

    Hello,

    Currently I am trying to use implicit styles with the RadDocking control but I am having an issue with the dragged floating windows.  When I attempt to drag a pane to move it elsewhere on the UI it goes invisible as soon as I start the drag.  When I drag the cursors around the screen I still get the compass appearing as if to dock at a specific direction.  Then when I drop them at one of the targets it rehosts the radpane but now without a header and can no longer drag it.  

    I am trying to start with the default style then modify it to fit my UI requirements but I can't even get the untouched style to work right.

    Additional Information:
    1. I am using an MVVM approach.  I have a list of objects that is bound to the PaneSource and the RadDocking control is creating the correct number of segments according to the bound list.
    2. I am using the No Xaml dlls provided.
    3. I have copied the necessary xaml files into project and have them referenced in a merged resource dictionary inside my user control.  (I have not modified these)
         a. System.Windows.Xaml
         b. Telerik.Windows.Controls.xaml
         c. Telerik.Windows.Controls.Docking.xaml
         d. Telerik.Windows.Controls.Navigation.xaml
    4. I am using the Q1 2014 version of the control.  

  2. Nasko
    Admin
    Nasko avatar
    588 posts

    Posted 13 Jan 2015 Link to this post

    Hi Aaron,

    The described behavior of RadDocking might be caused by inappropriate merging of the ResourceDictionaries - they should be merged inside App.xaml. This is because the ToolWindow is situated in a different scope (another visual tree) and it is looking for its style inside App.xaml.

    Hopes this helps.

    Regards,
    Nasko
    Telerik
     

    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.

     
  3. UI for WPF is Visual Studio 2017 Ready
  4. Aaron
    Aaron avatar
    2 posts
    Member since:
    May 2013

    Posted 13 Jan 2015 in reply to Nasko Link to this post

    Hey Nasko,

    Unfortunately I don't have access to the App.xaml file.  I was provided with a UI container dll that can load PRISM modules into it.  All that I can do is register the modules in a configuration file and then register my View (User Control containing the RadDocking control) to the  PRISM region that the shell has inside it.  

    Is there any other way to get the ToolWindow to look at a different scope other than the App.xaml?

    Regards,

    Aaron 
  5. Nasko
    Admin
    Nasko avatar
    588 posts

    Posted 16 Jan 2015 Link to this post

    Hello Aaron,

    When using implicit style the ToolWindow looks for its resources at the application level and this behavior cannot be changed. If you able provide us a sample project, we will check it our side and try to think of a possible solution that may help you. Meanwhile, please check the following links that provide some more detailed information about scenarios similar to yours and some approaches how to resolve it:
    http://stackoverflow.com/questions/8594178/wpf-prism-where-to-put-resources
    http://blogs.southworks.net/gmaliandi/2012/01/how-to-define-module-specific-resource-dictionaries-in-prism/

    We’re looking forward to hearing from you.

    Regards,
    Nasko
    Telerik
     

    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.

     
Back to Top