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
That is, currently I can only regret that this information was not published as a control limitation...
Tech support can check on the status of the issue but I can tell you that this issue (at least based on the description) is the same as several others reported and should be addressed in this next hotfix which should be available shortly. Since you've reported the issue you should be notified when the hotfix is available. The issue about focus shifting back is related since the ActivePane is based on the focused element but when using an HwndHost (WindowsFormsHost, WebBrowser, Frame with web url, AddInHost, etc) all are HwndHost based and when they receive focus keyboard focus is taken out of the WPF hwnd. In any case that aspect should be handled in the hotfix as well.
Hi Andrew,
I encountered the similar problem which is explained inside the error report (CAS-12213-APH13G). The DocumentHost becomes hardly usable when putting Winforms content inside. I posted request 2 days ago and it's still 'waiting assignment'. Moreover, I didn't see any solution to the problem neither among the bug reports nor inside the forum. One of our developers even reported me that similar strange behavior ( tab selection 'jumps' back) was noticed without winform inside.
Thanks.
If i use default TabControl in WPF then this problem does not happen. i have attached a sample app showing no problem when using default wpf TabControl.
I believe the issue has been reported but you should report the issue to the support group so you can be notified when a fix is available.