Pages in WPF are mostly intended to be used in browser like applications (usually with back and forward buttons) and hosted inside a NavigationWindow or Frame. Noesis does not implement those containers. Please create a ticket in our bugtracker if you require we support Frame or NavigationWindow in ...

Great, marking this as solved.

Hi, is exactly as you said, you are getting a pointer to the elements that define the template, not the ones generated for each ContentControl. There are ways to reach the runtime elements just by traversing the visual tree (using VisualTreeHelper), but it is a bad practice. Why don't you want to us...

Hello, There are different alternatives depending on each scenario. For example you can approach the navigation by splitting your different screens in several UserControls and then have a master/root xaml that references all of them and just changes the visibility to show/hide the active screen, lik...

Hi, you can share the same viewmodel (or code-behind) classes for Blend and Unity, you just need to use some conditional compilation to distinguish between the different types in WPF and Noesis/Unity. We use that approach in some of our examples, like in here: https://github.com/Noesis/Tutorials/blo...

Happy to help!

So the "magic" is just the Inherits flag? Interesting, I knew about the flag, but I thought there's something special in the TextBlock itself.

Yes, only that... this was an easy fix :)

Sure, note added to the bugtracker ticket with Android arm64 patched library.

The property is not registered with the Inherits flag, this is not correct.
Could you please create a ticket in our bugtracker and we will fix it?

Your workaround is the best solution right now.

Hi, we updated our code to be compatible for UE5.4 and will be available in the upcoming 3.2.4 version, which will be released in a few weeks. I attach a patch here in the meantime: Index: Plugins/NoesisGUI/Source/NoesisRuntime/Classes/NoesisRive.h ===================================================...