Hi all,
I’ve tried to look through the forum but I can’t figure out if there is the possibility to have relative custom properties paths in Vision. There is a way to reference a “parent” custom property without using the whole path?
My arrangement is as follows (imported SVG):
And the 616 S1 component has the following custom property:
What I want to do is binding the Visibility property of the “Line” component to a sort of indirect tag, taking the parent (616 S1) custom property in the path. But when I add the property it takes the full path to the component, like so:
so I can copy/paste the bindings between the heterogeneous components (i.e. parts of the SVG).
I need this because my layout is composed of different parts of the SVG with very different shapes and I want to be able to define the “Position” property on all the components, then copy/paste the bindings and having everything set up automatically.
I know that templates could help, but my problem is that not a single template could be used for all the layout.
I’ve read in other forum posts that copy/paste of the component will take with them the bindings updating property paths (if I’ve not misunderstood), but in my case I’m not copying the components (them are already part of the whole imported SVG).
Any suggestion or there is a different approach that I’m overlooking?
Thanks in advance.
No, unfortunately. Bindings are stored in the window, not in the component, so they always have to have complete paths. The designer will fix up bindings when copying and pasting components as if the bindings were relative, but that’s it.
When you say the designer will fix up bindings do you mean it should auto update a reference property path to the new parent component name automatically? I have a similar scenario where I have a few containers on each window with components that I am trying to setup indirect tag paths to using parent component custom properties.
Most of these have 2 references in the tag path. One of them is a window level custom property tied to the Root Container for the whole window so I never have to touch up that path. The 2nd reference in the tag path is tied to a custom property on the container that component is in. So if I made a button with the 2nd reference as "Root Container.Container 1.ProcessTagName" and copy paste it into Container 2, I still have to go to all the component properties and update that 2nd reference to be "Root Container.Container 2.ProcessTagName".
Are you saying the designer should be automatically updating that parent reference for me? Or am I misunderstanding what fixing up bindings means? If I copy paste all of Container 1, it will update every component's reference to be Container 2, but these containers also have some components that aren't using indirect paths so it would be nice if I could just copy paste the one component whenever I need to add a new one into some containers.
