I guess my machine was faster

Anyway, the trick here is just provide a change in the value to fire the trigger, so it is ok to use a bigger duration.
I'm glad it worked fine.

Looking at your code I see that you provide a different name to the dependency property "EnableToolTipHandler", than the one used in the static functions and the xaml "ToolTipHandler". Change your code to the following:     public class ToolTipHelper : DependencyObject     {     ...

Every View has a Root visual that allows Popups and ToolTips to show over the rest of elements. ComboBox drop down is added as a Popup to the View, so it is not a visual child of the ComboBox. If you want to test if mouse is over any element of the UI (including Popups and ToolTips) you should do it...

In Unity, we write messages to the Console window whenever we found warnings or errors processing the xamls. And if the xaml set in the NoesisGUIPanel contains errors, we also show in the component inspector a message to indicate it. You can see it here: http://www.noesisengine.com/docs/Gui.Core.Uni...

1. I found the bug, we were selecting the wrong item on mouse down when ComboBox had no focus. We will solve it for next release.

2. I don't understand, what do you mean for "larger than the main view"? Which visual are you passing as root in the VisualTreeHelper::HitTest call?

You're welcome

Hi, Sorry, the code I attached only works in Noesis. In WPF attached properties also require a static getter and setter for the property. If you type 'propa' in Blend or Visual Studio it will provide you a code snippet for an attached property that looks like this: public static int GetMyProperty(De...

You are using the native runtime library, instead of the library that comes with the Unity package.
NoesisGUI 1.2.6f5 unity package should already include a libNoesis.so under Plugins/Android/libs/x86.

Try to import again the package and make sure you have that file checked.

The folder where you place the files shouldn't matter, because the namespace could be whatever you want. What you have to make sure is that the xaml is correctly processed (without errors) after the InvokeCommand class is compiled and available in the assembly. Try to rebuild xaml resources to see i...

I made a simple example to show you how can be done, it is working fine for me. InvokeCommandTestBehavior.cs using UnityEngine; using System.Windows.Input; using Noesis; namespace Assets.InvokeCommandTest {     public class InvokeCommand : FrameworkElement     {         public static DependencyPrope...