We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: November 16, 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

DockingManager: WinForms control not visible after state change

Thread ID:





88418 Jul 22,2009 01:02 PM UTC Jul 22,2009 01:56 PM UTC WPF 2
Tags: Tools
Robert Koelz
Asked On July 22, 2009 01:02 PM UTC

next problem

i have a custom control which hosts a winforms control on the left side and a contentpresenter on the right side to show different views depending what is selected on the left side. when i put this custom control into the docking manager and start dragging it, so it changes the state from dock to float, the winforms control gets invisible. but it is still there, so when i click at some point in this empty area the views get changed on the right side.

when the DockStateChanged event gets fired i tried to call UpdateLayout and InvalidateLayout for the manager and the sender (my custom control) but nothing happens.

Robert Koelz
Replied On July 22, 2009 01:27 PM UTC

when i dock it back, the winforms control is visible again

Balavasanth [Syncfusion]
Replied On July 22, 2009 01:56 PM UTC

Hi Rob,

Thanks for your interests in Syncfusion products.

In order to use WFH element in a WPF application, we need to set UseInteropCompatibilityMode property to true to make the Docking Manager to be compatible with the WFH. Kindly set UseInteropCompatibilityMode to True in your sample.

Make use of the code snippet for more idea.



Constraints in hosting a WFH in a WPF application

There are some complexity involved when a Windows Forms control is hosted in a WPF control. To explain this, we have a sample using the standard Microsoft WPF Controls with WFH in it. Following are the limitations of the WPF framework with a Windows Forms Host which is clearly explained in the sample.

• In a WPF application, when you add a Windows Forms Host control, it will always render at the top layer of the WPF element, which is the default behavior of the WPF Framework.

• WFH in WPF cannot display a transparent pop up.

• In the sample, MouseLeave event is raised for WPF border when we move the mouse over its child ( WFH )

• WFH doesn''t support animation;

• Doesn''t support routed events.

Please let me know if you have any questions.



This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

or the page will be automatically redirected to sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon