Relative Tag Path binding to templates?

Hi, I've been playing with the inheritance of some of our projects and also the templates.

So far my templates have a property that will point to the path of a tag so the binding can be transferred correctly. Now we create our main project and we inherit that to the actual projects that need to be created by a third party.

It has become a hassle that a single template is repeated several times in the same project due being in all the windows is there a way we could do something similar to relative tagging on the template properties? The only section that changes is the Provider and the first folder.

I'm trying to find something simple without having to do much on scripting but it push comes to shove then will look into scripting.

I recommend that all indirection for templates and windows pass a complete tagpath prefix, as a single string, pointing at either a folder or a leaf tag. Including the tag provider.

When such tag paths need to passed inward to nested components, only a suffix needs to be added for the inner object.

Once done, there no further restrictions on tag path or folder depth when re-using the template or parameterized window.

(All of this applies to Perspective, too.)

3 Likes