My Noesis.Build.cs does include those lines. I did a clean integration by deleting the previous Plugins/NoesisGUI dir and copying in the new one. Edit: I typically run the debug editor, so I switched to development and it built correctly; I then switched back to debug and that too built fine. Must h...

Example: Plugins\NoesisGUI\Source\NoesisEditor\Private\NoesisEditorModule.cpp(60): fatal error C1083: Cannot open include file: 'NsApp/LangServer.h': No such file or directory I can adjust the include paths to NsApp headers to be more specific, and they build, but I guess it shouldn't be like this.

Right, in the end using hardware cursor is probably the right way to go, but it was a fun experiment!

Nevermind, I got this working by making some changes to NoesisInstance.cpp. First I made a duplicate of NoesisHitTestVisibleTester and the HitTest(FVector2D) function, called NoesisHitTestVisibleIgnoreTransparencyTester and HitTestIgnoreTransparency respectively. Then in the new hit test struct, I c...

Hi, I'm using UE5.1 and want to use Noesis to render a cursor that is always visible on screen. I have achieved this by hooking the MouseMove event in my view, grabbing the mouse coordinates, then setting them to the cursor's view model. The root element also has a transparent background so that mou...

It's looking for the reflection type id, not the class namespace.

Change
NsMeta<TypeId>("MouseWheelBehavior");
to
NsMeta<TypeId>("NoesisApp.MouseWheelBehavior");

Hi, I've moved this over from the bug tracker for the benefit of a wider discussion. 1) What framerate does Noesis typically target, and how is this determined? Does it automatically match the framerate of the engine (e.g. Unity)? I understand in WPF the framerate is dynamic, varying between 0 and a...

Unkown, the roadmap is dead, bug reports seem to have had no movement on them for months, but the devs are present on the forum.

This is possible using inlines, which are supported, but non-text elements require WPF's InlineUIContainer, which isn't supported. Having the buttons as font glyphs may provide the most flexibility for you in terms of localisation and compatibility of text rendering. Since it's only a single line of...

Noesis is effectively a drop in replacement for WPF. Avalonia is WPF inspired, but it's not WPF really. Integration of Noesis really depends on what you want to integrate it into. Native or managed? Do you intend to integrate into an engine? You can read more about that here http://www.noesisengine....