It is possible that you are not registering the converter for the enum: RegisterComponent<EnumConverter<SignInTransitionStates>>(); You need to do that in order for the XAML parser to understand the string used in Value="SignInIntro". We are doing this in our Menu3D demo: https://github.co...

You should use the new b: namespace because it is what our Noesis.GUI.Extensions nuget is exposing to Blend, although internally for Noesis it makes no difference if use one or the other.

Popups are always added to a layer that stays on top of the rest of the UI, so using ZIndex here won't help.

The solution could be to have a different View only for the keyboard, that way you are in control on the order of how things are rendered.
Could that work for you?

I tried binding IsEnabled on a button to a bool in my View BP, just like the text/value properties, but that does not work Hi, you should be able to bind to a boolean property. I just tried a simple example like this: <Grid xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"...

Also, it's not related to the issue but, I could take this opportunity to mention a few things I noticed in the docs as I was browsing: In both of these links below, in their respective xaml demo, the <b:Interaction.Triggers> tag is not closed. Also in the GamepadTrigger Class description for the &...

I verified that WPF does not raise any error or warning when removing a handler from an event that was not previously registered, so this is wrong in Noesis. Could you please report it in our bugtracker, we shouldn't show any error message in that case either. In the meantime one simple workaround w...

This is a bug in Noesis handling Type properties, could you please report it in our bugtracker?
I will provide a patch for you to try there.

So it is the control that uses the data who knows (through the attached property) if it has to reference the entity directly or the target. Then, if the attached property is set in the control, and assuming the control is the root of the xaml you could have: <UserControl x:Class="TheNamespace.M...

how can I use this information for resizing them? Each control has a number of properties to know when they are focused: - IsFocused indicates it has the logical focus - IsKeyboardFocused indicates it has the keyboard focus (only one element in the whole UI can have keyboard focus) - IsKeyboardFocu...

Hi, From a layout point of view this is just a Grid with 2 columns and 3 rows arranged like this: <Grid> <Grid.ColumnDefinitions> <ColumnDefinition Width="3*"/> <ColumnDefinition Width="2*"/> </Grid.ColumnDefinitions> <Grid.RowDefinitions> <RowDefinition Height="Auto"/>...