A couple of questions:

• Is the Canvas the direct logical child of the UserControl? I mean: UserControl.Content = Canvas?

• Does the UserControl have its Background = Transparent? Because UserControl default template looks as follows:

<Border

Background="{TemplateBinding Background}"

BorderBrush="{TemplateBinding BorderBrush}"

BorderThickness="{TemplateBinding BorderThickness}"

Padding="{TemplateBinding Padding}">

<ContentPresenter

HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"

VerticalAlignment="{TemplateBinding VerticalContentAlignment}"/>

</Border>

Apart from that our default templates have a default Background = Transparent in the following controls: Label, RadioButton, CheckBox, ScrollViewer, ListBoxItem, MenuItem, ComboBoxItem, TreeViewItem, StatusBarItem, and ListViewItem. But these are required to properly click them with the mouse.

If you can attach a minimal project where this can be reproduced we can debug it and find what is occurring.

Thanks for your collaboration.

Thanks! yes - it was a background=transparent causing the hit test to occur. Removing it canceled hit testing as well. Note that the behavior where hit testing is being ignored looks like a WPF bug: https://social.msdn.microsoft.com/Forum ... ?forum=wpf
I propose to deviate from WPF on this one since it's obviously an issue if hit testing returns elements with IsHitTestVisible == false. It's great that you value compatibility so much. In this case, perhaps it's a good idea to fix the bug and have a list of "Fixed in Noesis" differences somewhere compared to WPF. What do you think?

And yes, the Canvas is a direct logical child of the UserControl

For completeness:
<UserControl x:Class="FantasiaPhone.UnityImageFrame"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
Background="Transparent" IsHitTestVisible="False">
<Canvas x:Name="frameRoot" IsHitTestVisible="False">

ai_enabled has good suggestion in the forums: add a HitTest overload with boolean flag to allow IsHitTestVisible = false to work. http://www.noesisengine.com/forums/viewtopic.php?f=3&t=1170&start=90#p7473

In addition, can be mentioned somewhere in docs as "beneficial deviation from WPF behavior".
What do you think?

We decided to implement in C# the callback version of the HitTest function.
This will work for any situation and makes code compatible with WPF.

Thanks, sounds good! hopefully not too taxing on the system due to pinvoke-s (can't really tell without profiling)

Please give higher priority to the implementation of the C# HitTest method with the callback delegate for the next update.
Without it, we have to rely on a very problematic and complex workaround code.

Note: having a callback, while good idea, may have significant performance implications if we have to switch from managed to native code.
In addition (or instead of) to callback, can we have a boolean parameter e.g. "emulateWpfBehavior" that is true by default and mimics the WPF bug, and false otherwise?

(to be fair, I think the WPF behavior is just a bug, ideally Noesis fixes it in your implementation and you work better than WPF on this one. There's no reason why an IsHitTestVisible==false should ever hit)

Yes, having a parameter or simply another method will be good enough for our needs. When it was discussed on the forums, I've also supported this much more efficient approach.

Any updates on this?

We decided to implement in C# the callback version of the HitTest function. This will work for any situation and makes code compatible with WPF.

Haven't work on this yet but is something we are going to address before releasing the final 2.2 version.

Thanks for the fix!