Accessing document custom tag property members the same way as document tag members

[pturmel]

Primary description of the differences:

Automation Professionals' Integration Toolkit Module

I don't know all the details of tag()'s problems, but I suspect there are two key contributors: tag() startup tries to supply a proper initial value, with a 1-second timeout, on startup everywhere it is used. Use a hundred tag() calls in the bindings on a Vision template or window and you can block your UI for up to a hundred seconds, looks like. Not sure how Perspective's parallelism fits here, but you'll either tie up a thread for a hundred seconds, or tie up a hundred threads from the Per…

For a single tag, an indirect binding will be better than my tags() function.

Edit: See new beta that may be useful to you:

Automation Professionals' Integration Toolkit Module

New BETA. Alters the tags() function to not use the tags' own qualities for its function return quality. This enables other iterators to wrap tags() without using forceQuality(), which has the side effect of obliterating any nested non-good qualities. Adds the new qvAt() function which re-implements the square bracket operator to not discard nested qualities. For Ignition v8.1: v2.1.1.250881822 You can now supply prune the list of returned tag path/value pairs to exclude non-good quality wi…