Template Drop-Target Binding and Leased Tag Groups


Just curious if when I bind a UDT (let's say a large data structure) to a template for the convenience of drag-and-drop template placement on a vision window -- does that automatically put all of the tag elements within the UDT into "Leased/Driven" mode set by the tag group (e.g., the faster scan rate), rather than the base rate? Would like to increase the efficiency/speed of resolving the binding in our graphics -- but am unsure of the impact of adding the full UDT as a property of my template...

If all tag properties of the template get switched to "Leased/Driven", it seems like quite a bit of a waste if I'm only displaying a few of the UDT tag members in that template onscreen... Really hoping the rate only switches for the few that are displayed within the template...

Thanks in advance for any info/insights!


There are numerous performance hits to using UDT parameter types. Just don't. Pass a tag path and indirect bind what you are actually using. Much more performant and allows you to pass any tagpath that has the relevant sub-elements, not just instances of a specific UDT.

UDTs are wonderful for creating and maintaining large numbers of tags. Not so wonderful elsewhere.

I can't answer your actual question because I am never in that position, and you shouldn't be either.


Thanks for the intensely fast reply, Phil! :slight_smile:

Thinking Inductive should include some of these limitations/notes in their documentation, or remove this functionality altogether! Would be great if the default "drop" action was the tag path... would make life much easier

1 Like

IA doesn't always agree with me. :man_shrugging:

1 Like