Pane Navigator problem with nested XamDockManagers

State See Verified Answer
Replies 2 replies
Subscribers 5 subscribers
Views 702972 views
Users 0 members are here

XamDockManager

315

Patrick posted over 15 years ago

I found the PaneNavigatorButton not working properly when using nested DockManagers.

   1. Compile and execute the attached code
   2. Press the PaneNavigatorButton or press Ctrl+Tab
   3. Pane Navigator of outer DockManager is shown (= OK)
   4. Focus the inner DockManager (i.e. select Tab "Doc 2")
   5. Press the PaneNavigatorButton or press Ctrl+Tab
   6. No Pane Navigator is shown (= problem)

Is this a known problem or is something wrong with my code?

Thanks,

Patrick

Same Code as in attachement

xaml:

-----

-----

xaml.cs:

----

using Infragistics.Windows.Controls.Events;
using Infragistics.Windows.DockManager;

namespace WpfTest
{
    public partial class Window2
    {
        public Window2()
        {
            InitializeComponent();
        }

        private void XamDockManager_ExecutingCommand(object sender, ExecutingCommandEventArgs e)
        {
            if (e.Command == DockManagerCommands.ShowPaneNavigator)
            {
                e.Cancel = true;
            }
        }
    }
}

----

NestedDockManager.zip

315

Patrick posted over 15 years ago in reply to Andrew Smith [Infragistics]

This solution works if both XamDockManagers are declared in the same XAML (which is only the case in my simplified example). In a real world application the workaround would be more like:

if (e.Command == DockManagerCommands.ShowPaneNavigator)
{
    e.Cancel = true;

    FrameworkElement fe = Parent as FrameworkElement;
    while (fe != null && !typeof(XamDockManager).IsInstanceOfType(fe))
    {
        fe = fe.Parent as FrameworkElement;
    }

    XamDockManager outer = fe as XamDockManager;
    if (outer != null)
    {
        outer.ExecuteCommand(DockManagerCommandsShowPaneNavigator);
    }
}

Thanks for your answer,
Patrick
Cancel
Reply

Cancel
54937

Verified Answer
Offline Andrew Smith [Infragistics] posted over 15 years ago

I was able to get the behavior you described using your sample. I submitted the issue for review. The issue relates to the fact the inner dockmanager assumes that it can execute the showpanenavigator command so essentially it gets the command routed to it for execution only to have it cancelled by the executing command. For now, you could in the inner dockmanager execute the command for the outer dockmanager.

if (e.Command == DockManagerCommands.ShowPaneNavigator)

{

e.Cancel = true;

this.outer.ExecuteCommand(DockManagerCommands.ShowPaneNavigator);

}
Cancel
Reply

Reject Answer

Cancel