I Am Using Ipaddress Control Derived From Windowsformhost. But When I Scroll Down My Widget It Is Floating Outside Of Widget.Any Solution Will Be Appreciate.

Question

0.00/5 (No votes)

See more:

xmlns:ipBox="clr-namespace:IPAddressControlLib;assembly=IPAddressControlLib"

XML

<local:WindowsFormsHostExtended Grid.Column="1" Grid.Row="1" Margin="40,15,3,0" Width="150" VerticalAlignment="Stretch" HorizontalAlignment="Stretch" ScrollViewer.HorizontalScrollBarVisibility="Auto" ScrollViewer.VerticalScrollBarVisibility="Auto">
          <ipBox:IPAddressControl x:Name="IPAddress" TextChanged="IPAddress_TextChanged" />
      </local:WindowsFormsHostExtended>

Posted 25-Aug-15 5:14am

Member 11892033

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Accepted Answer · 2015-08-25T06:49:00

This is a well-known problem with WPF/WinForms interop, often referred to as the "airspace" issue. WinForms controls added to a WPF window have severe limitations:

WPF and Win32 Interoperation Overview[^]

HwndHost cannot be rotated, scaled, skewed, or otherwise affected by a Transform.
HwndHost does not support the Opacity property (alpha blending). If content inside the HwndHost performs System.Drawing operations that include alpha information, that is itself not a violation, but the HwndHost as a whole only supports Opacity = 1.0 (100%).
HwndHost will appear on top of other WPF elements in the same top-level window. However, a ToolTip or ContextMenu generated menu is a separate top-level window, and so will behave correctly with HwndHost.
HwndHost does not respect the clipping region of its parent UIElement. This is potentially an issue if you attempt to put an HwndHost class inside a scrolling region or Canvas.
While the mouse is over the HwndHost, your application does not receive WPF mouse events, and the value of the WPF property IsMouseOver will be false.
While the HwndHost has keyboard focus, your application will not receive WPF keyboard events and the value of the WPF property IsKeyboardFocusWithin will be false.
When focus is within the HwndHost and changes to another control inside the HwndHost, your application will not receive the WPF events GotFocus or LostFocus.
Related stylus properties and events are analogous, and do not report information while the stylus is over HwndHost.

There were plans to fix this in .NET 4.5; unfortunately, the relevant properties were dropped in the final release:
Mitigating Airspace Issues In WPF Applications[^]

There was a UserVoice suggestion to bring these beta features back, but that was declined:
Bring back the HwndHost.IsRedirected and CompositionMode[^]

There are various workarounds which attempt to solve the problem (eg: Over-coming the Interop Airspace Issue in WPF[^]). However, there's no guarantee that they'll work as you need them to.

The best solution is probably to try to recreate the control in WPF.