Hello! I am wondering about the intended set up for binding data to a property that is nested in a template, or a template inside another template. Say I have a button template with an image that I want to be bound to the data context for the menu page that the button is in. Should the button itself have a data context binding, or should it use a custom property to pipe the image property from the menu page's data context to the button template?

I was trying to do the latter, and use custom properties to pipe data bindings into templates, but I ran into another question. This set up works well for basic properties, but I can't make it work if I try to use one of my custom data structures as a custom property type. I can set up the custom property as expected, but I can't seem to bind anything to the inner data of the structure. Is this a known limitation of custom properties, or is there a different approach I should use here?

Hi,

The workflow of exposing custom properties to pipe data into templates it is correct.

I verified we have an issue when defining custom properties with data structures as types, the property is not correctly registered. Could you please report this problem in our bugtracker?

In the meantime you can use "BaseComponent" as the type in your custom property to bind any data structure instance. Could you try that?