Hello,

I think this may be related to a know issue introduced in Noesis SDK 3.2.4. Could you please create a ticket on our bug tracker and paste the link, so I can send you a patch?

Thank you!

Hi,

I just made a quick test and it worked without issues. Could you please create a ticket? It may be related to the specific XAML you're using.

Hi,

Sorry, a bug was introduced in 3.2.3 that we didn't fix in time for 3.2.4.

Please, create a ticket and I'll provide you with a patch you can use until the issue gets resolved.

Thanks!

Hi,

Are you registering your converter? You can see how we do it in our DataBinding sample. We register them in the Game module's StartupModule function and unregister them in the ShutdownModule function.

Please, let us know if that helps.

I've replied on the ticket.

Hi again.

Could you please create a ticket on our bugtracking portal? I have a patch for you to try. It's all plugin code, so you can apply it on your side until we publish a new version.

Thanks!

I'm sorry, I'm still looking into it. I'll do my best to figure it out before the end of the day.

Hi,

What's the behavior you're expecting? If I'm getting it right, you want the input to be handled by the player input after the drag and drop, and not by the UI. Am I right? If so, which input mode are you setting on the PlayerController?

Thanks

Hi, The way to do it, once you've loaded the XAML text, is to create an UNoesisXaml and set its XamlText property. UNoesisXaml* NoesisXaml = NewObject<UNoesisXaml>(); NoesisXaml->XamlText.Insert((uint8*)XamlText.c_str(), XamlText.length(), 0); However, take into account that if the XAML depends on o...

Hi, The easiest way to do it is to set a DataContext on your NoesisInstance, and then use a Binding on the Command property of your Button. You can see an example in our Buttons Sample (the three buttons are at the bottom of the XAML). In that sample the DataContext is a Blueprint, but you can use a...