Hey Noesis Forum,

With our game, after we set up data bindings to the backend info, for example data structure and sets for stats for items in an inventory, when returning to noesis the elements bound to this data is no longer visible as obviously Noesis doesn't have a point of reference for the binding any more.

Is there a way without disconnecting the databindings to the back end of the game to keep elements visible in noesis studio?

Hi Ken!

Can I just confirm with you your situation -- am I correct in understanding that you have set up Data Structures and Data Values in-Engine, but when inside Noesis Studio, you are not seeing your UI reflect this in-Engine Data?

Additionally, you mentioned that you have Bindings set up in Noesis Studio. What Data are these bound to there? (For example, do you have Properties bound to the Data in Studio's Data Panel?)

Is there a way without disconnecting the databindings to the back end of the game to keep elements visible in noesis studio?

Part of the beauty of the framework, is that both the XAML files that make up the interface, as well as the all of the Bindings contained within these stay the same regardless of which Data context the interface is using (ie: Engine vs Studio). So there should be no need to change/disconnect any Bindings you've set up in your interface as you move between Studio and the Engine.

Looking forward to diagnosing this further!

- Dorian

Hey Dorian!

am I correct in understanding that you have set up Data Structures and Data Values in-Engine, but when inside Noesis Studio, you are not seeing your UI reflect this in-Engine Data?

To the best of my understanding, yes. After connecting/binding our data from the back end, these elements such as stats, listbox items and even media stop displaying in Studio.

From my understanding of what you've replied with there should be a way to stop this and keep those elements visable?

Hi Ken,

Bindings that work in-game don't function automatically in Studio, because at design-time there's no active data context. To enable bindings in Studio, you'll need to recreate your enums/structures, populate them (via data sets), and then set the design-time data context manually at the root element.

Once we release the Studio SDK, you'll also be able to extend Studio to include your engine's data classes directly.

We're still working on the documentation for this, thank you for your patience.

In the meantime, to better understand your issue, could you please share a minimal XAML example that reproduces the problem?

Thanks for the update jsantos!

Exciting to hear about the connection between studio and engine! That will definitely be a powerhouse!

I'll work on getting a minimal xaml over asap!