I have a sample application which contains a XamlDockManager as the content for a XamRibbonWindow. In that dock manager I have a number of TabGroupPanes and a DocumentContentHost. As I drag a TabGroupPane over the center drop zone of the DocumentContentHost pane, the application locks up with the exception in the subject line. Sometimes it take a couple tries, but I seem to have isolated it pretty well and can easily and consistently reproduce in a few seconds.
It looks like I can drag around all day in other TabGroupPanes, including the center drop zone of each, and I can create a new SplitPane in the DocumentContentHost. I just can't dock it this one way.
In researching this further, I thought I'd use a workaround and set the AllowInDocumentHost property to false on the TabGroupPanes. When I do that, I don't get the center drop zone highlight, but it seems to catch an edge or something and will still fail.
Not being able to dock TabGroupPanes in the DocumentContentHost is actually preferred in our app. Is there a way to disable it altogether so you don't even see the adorners on the DocumentContentHost?
Here's the markup for the dock manager. We're using version 9.1 with I think the latest service releases.
<igDock:XamDockManager x:Name="dockManager"><igDock:XamDockManager.Panes><igDock:SplitPane x:Name="ExplorerSplit" igDock:XamDockManager.InitialLocation="DockedLeft" Width="225"><igDock:TabGroupPane x:Name="ExplorerPane"><igDock:ContentPane x:Name="Explorer" IsPinned="True" Header="Explorer"><Button Content="Explorer" IsEnabled="False" /></igDock:ContentPane></igDock:TabGroupPane></igDock:SplitPane><igDock:SplitPane x:Name="ListSplit" SplitterOrientation="Vertical" igDock:XamDockManager.InitialLocation="DockedTop" Height="145"><igDock:TabGroupPane x:Name="ListPane"><igDock:ContentPane x:Name="List" IsPinned="True" Header="List"><Button Content="List" IsEnabled="False" /></igDock:ContentPane></igDock:TabGroupPane></igDock:SplitPane><igDock:SplitPane x:Name="DetailSplit" SplitterOrientation="Vertical" igDock:XamDockManager.InitialLocation="DockedRight" Width="270"><igDock:TabGroupPane x:Name="DetailPane"><igDock:ContentPane x:Name="Detail" IsPinned="True" Header="Detail"><Button Content="Detail" IsEnabled="False" /></igDock:ContentPane></igDock:TabGroupPane></igDock:SplitPane></igDock:XamDockManager.Panes><igDock:DocumentContentHost x:Name="DocumentHost" Background="DarkGray"><igDock:SplitPane x:Name="DocumentsSplit" SplitterOrientation="Vertical"><igDock:TabGroupPane x:Name="DocumentsPane" TabStripPlacement="Bottom"><igDock:ContentPane x:Name="Document" Header="Document"><Button Content="Document" IsEnabled="False" /></igDock:ContentPane></igDock:TabGroupPane></igDock:SplitPane></igDock:DocumentContentHost></igDock:XamDockManager>
Thank you, Andrew.
Yes the problem appears to have been the graphics card drivers. I am using a NVIDIA Quadro NVS 450 Graphics card.
The problems only appear to manifest when using their proprietary "MultiView" mode.
I'll keep a watchful eye to make sure this problem doesn't reoccur.
Thanks again for your suggestions.
I've had it crash consistently within LiveMeeting when trying to float a pane. I'm running VS 2008 SP1 with framework 3.5 SP 1. I am having a very hard time reproducing this, but it does exist and the only reliable workaround is to restart the machine. Sometimes I connect via Remote Desktop through Live Mesh, but I have the same difficulty trying to reproduce.
I have yet to be able to reproduce this. NotifyPartitionIsZombie usually means that something has caused a problem on the render thread. In searching around I find several reports of NotifyPartitionIsZombie (see below list of links) - many of which reference a possible bug in the wpf framework having to set AllowTransparency to false so perhaps that's related - the drag indicators and docking indicators will have this set to true so they can be semi-transparent (i.e. use layered windows). I know you mentioned that you have VS 2008 SP1 but can you make sure that you have 3.5 SP1 (i.e. the .net framework version).
http://social.msdn.microsoft.com/forums/en-US/wpf/thread/b2aa4601-3f66-4dd6-8a20-0744265c5f1c/
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=321955
http://social.msdn.microsoft.com/forums/en-US/wpf/thread/f3fc5b7e-e035-4821-908c-b6c07e5c7042/
It could also be video driver related so perhaps if you could list your specs then perhaps that would help. Are you able to reproduce this on other systems? I've also seen some mention of this error occurring (without our components) when running within a remote desktop session but I'm assuming since neither of you mentioned this that this isn't the scenario in question.
Could someone from IG please indicate whether you are still looking into this? This is a critical bug that crashes all WPF apps running your dock manager.
Crashed on me during a demo yesterday - infront of a lot of people.
I just got the sample above to crash in a vanilla project. Just repeatedly docking and undocking. For the first few minutes nothing. Then for another minute I just grabbed a pane and waved it repeatedly over the main docking window, without releasing the button. Then I grabbed the main window and resized to half the screen (don't know if that was coincidence) - It crashed the next time I pulled the tab