Hi,
I am using DockableControlPane and displaying it as floating in the WinForm say Form1
This Form1 is used in the WPF application using System.Windows.Forms.Integration.WindowsFormsHost.
I am navigating from Form1 to Form2 using System.Windows.Navigation.NavigationService after the Form2 is closed again I am navigating to back using NavigationService.GoBack().
But when I come back to Form1 the DockableControlPane which is in floating mode goes invisible and its closed property is false.
Hello ,
Is it possible to post a small sample where your issue is reproducible in order to investigate this further for you.
I am waiting for your details.
Publish TestInfra project and then Open the xbap application from published directory.
1. Write some text in TxtBox
2.Click Show the Window
3.Click on Navigate
New form launched
4.Click on close
(Observe that changes in Textbox are retained which means same instance is opened.
However Floating window is not displayed.
Missed the TestInfra file in previous reply hence uploaded.
I just wanted to know if you were able to solve your issue based on my suggestions or you still need help? Just let me know.
Thank you.
Hello,
I am just checking about the progress of this issue. Let me know If you need my further assistance on this issue?
Thank you for using Infragistics Components.
You could call this methods manually, when you came back through NavigationService. When you host a Windows Forms controls in WPF, you should keep in mind that you will meet some limitations caused by the different way on which both platforms work. For more information please review the following links:
http://social.msdn.microsoft.com/forums/en-US/wpf/thread/85c6b75a-164f-4519-bea3-b8790f1601fb
http://blogs.msdn.com/b/scoberry/archive/2006/09/01/735844.aspx
One of the limitation is the “Focus”, which I believe is the main reason for your issue. Please nothe the “Focus” section in the second link.
Please let me know if you have any further questions.
SuspendLayout() ResumeLayout() didn't solve the problem.
These events were not fired if we came back through NavigationService.
But this is not the solution its the workaround.