I'm using xamDockManager in my WPF application but I need to use a webbrowser control. So in my DocumentContentHost I have a WidowsFormsHost wrapping the WinForms webbrowser control. This all works fine except for when I have an unpinned dock panel. The panel pops out when I move the mouse over the header but the panel draws behind the webbrowser. If I pin the panel the the webbrowser is correctly resized and everything is fine. It's just when the dock panel is in the unpinned state that it appears behind. Any way I can fix this or will I have to go the the beta WPF webbrowser?
Thanks,
Adam
I am doing exactly the same thing and running into the exact same problem.
Webbrowser control wrapped in WindowsFormsHost control, hosted by DocumentContentHost. When unpinned and hidden panel files out, it sildes behind the Webbrowser control.
This is slightly different than the issue to which I was referring. This happens because the flyout panel is not hosted within a separate window and therefore all the elements (the xdm and the flyoutpanel) are hosted within the same os window whereas the webbrowsercontrol is in its own child window. You should report this issue to the support group. We'll probably have to add an option to have the flyout panel hosted within a popup since there are limitations to how a popup can be used - e.g. it will adjust its own position such that it never renders across screens.
I have reported this via support. Here is the response (hope you dont mind me posting it, but thought it may help others):
It is expected that the control(s) on a WindowsFormsHost will be drawn over the fly out for the SplitPane when the pane is collapsed. This is due to the ‘airspace problem’ that you referenced when you logged the case.Since the WindowsFormsHost will create a separate HWND, it will draw over any WPF elements on the Window containing the WindowsFormsHost. This information is available in the “Layout Considerations for the WindowsFormsHost Element” on MSDN:http://msdn.microsoft.com/en-us/library/ms744952.aspxNote: The above link isn’t owned or maintained by Infragistics.
The drop down for the application menu of the XamRibbon will appear over controls hosted in a WindowsFormsHost because the drop down is actually another HWND which doesn’t cause an airspace violation like the XamDockManager and the WindowsFormsHost.If you can create another HWND where the fly out of the SplitPane is, you may be able to work around this issue. This would either be done by modifying the Templates for the XamDockManager and possibly using a Popup of by responding to the mouse over of the tab for the fly out and then showing a Popup then instead. I am not sure about the implementation details of either of these or if they are even feasible.
The response is correct in explaining why it is happening and as mentioned in the referenced link, it is an expected behavior that windowsformshost will appear over other elements. That being said, it is feasible for us to workaround the issue with regards to the flyout panel since we are creating it in code and there is an understandable expectation that the flyout panel's contents be displayed above other elements in the window - including a WindowsFormsHost. As I mentioned there will be ramifications/limitations (and there could be others - e.g. animations may not be as smooth, etc.) to doing this so likely we would have to do this as an option (i.e. add a property). I would recommend replying back about this issue and request it be reopened/reviewed.
Note, the issue with regards to airspace should be addressed in the next hotfix for v8.2 and 9.1. That is, if you are using a WindowsFormsHost or other HwndHost (e.g. WebBrowser) then the contents of the unpinned pane (i.e. the flyout) and the preview of the PaneSplitter should be displayed above the HwndHost control. If you would like to be notified when the hotfix is available you should be sure to submit an issue to the support group.