Building full tag paths vs. indirect tag bindings

Ignition
1

Hi all,

I'm looking at the "Perspective Faceplate Library" from Ignition Exchange and trying to understand something...
When creating parameterized objects and faceplates, I would normally pass in the tag path and use indirect tag bindings. On this project though, the tag path is passed in and then custom properties are created using property bindings to the tag path and then a script transform to return the full path to the tag. Then throughout the faceplate, expression tag bindings are used which reference the full tag paths in the custom properties.

I'm trying to understand if there's any advantage to doing this vs. just indirect tag bindings?
Wouldn't an indirect tag binding provide better performance than going through all these extra steps?

Ignition Exchange does note that this project was created for the 2021 ICC build-a-thon, so maybe the project was written in this way to meet certain build-a-thon requirements.

image
image1145×607 95.2 KB

2

Whoever designed that doesn't know how bad that is for performance. Don't use a script transform where an expression will do, and use neither just to perform the string concatenation that an indirect binding will naturally offer.

3 Likes
3

Thanks Phil !
You described exactly what I was thinking, but I just wanted to be sure I wasn't missing something.
Appreciate the reply.

4

this is designed by a winCC user, working like this is required there