This is something odd, when a contentpane is undocked and moved into a floating state PRISM V4 RegionManager seems to loose a reference to that ContentPane's injected region, causing some of my code that depends on this to fail.
Note: Re-docking seems to add the region back into the RegionManagers collection.
Any suggestions? I can probably figure this one out or a way around it but i wanted to bring it to your attention and see if perhaps you already have a solution.
Use this Prism region adapter for the XamDockManager
http://brianlagunas.com/2012/09/12/xamdockmanagera-prism-regionadapter/
I'm not sure I follow. There really is no distinction. The xamDockManager creates the floating panes whenever it needs them to host a floating splitpane. If you needed to somehow distinguish you could set a property on your root splitpane that you create at design time and if that property isn't there then it's one that has been created but then again if you load a layout the dockmanager will create the panetoolwindow as needed.
This seems to have done the trick. One more question though, what is the best way to see if a floating window is being created vs. the standard "ToolWindowLoaded" events that are fired during initialization for my docked SplitePanes?
Floating panes are hosted in a separate WPF Window so you probably need to handle the ToolWindowLoaded event and use the RegionManager.SetRegionManager method to set the region manager on the e.ToolWindow.
Hi,
Same Problem here!
How can I fix this?Thanks in advance!