Hi Otter, The LocExtension was designed to use static keys, because our understanding was that any dynamic data will be provided by the MVVM itself. So instead of using the LocExtension you would directly use a binding on the target property, and the binding will provide the translated data. <DataTe...

Hi, which Blend project are you using? Is the one included with the Unity samples when you import them?
Because I just installed 3.2.3 version into Unity, imported Inventory sample, opened the Inventory-blend.sln file included, built the solution and got no errors.

Try returning the value as a float, because I guess this converter was applied to the Width property of a UI element, right? return (float)(width * factor); There is a known issue regarding the values returned by converters, 1376 , so for now the converters need to return the type of the target prop...

Hi, what do you mean by "multiple view models that can operate concurrently"? A View can only be connected to a single view model at the same time, but inside the View you can point to different properties to access several sub-view models: <Grid DataContext="{Binding ModelA}">.....

String properties are a bit different in Noesis compared to WPF because in C# strings are reference values that can be null, but not in C++. So if the binding path is correct and the property returns an empty string then the binding will just use that value (no FallbackValue or TargetNullValue). If ...

The FallbackValue is used when the binding cannot be resolved (the property in the binding path can't be found for example). If the binding was correctly evaluated but the return value was just null, then you should use the TargetNullValue property of the binding. In the following xaml the second re...

The RichText exposed in Noesis is based on the use of Styles as explained in the tutorial you linked. So each of the tags you specify in the text, like <char>, is mapped to a Style defined in your xaml resources. In the upcoming 3.2.3 version we improved the RichText extension to support not only st...

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?