From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
I would like to see it going even a step further. Like we have a static VI reference and a strictly typed VI reference as you propose only that the strictly typed VI reference inherits all settings from the VI as is set in the properties of the VI not just the reentrant behavior.
The Open VI Reference function includes the following change:
Thevi pathinput parameter now accepts an existing VI reference in addition to the string and path data types accepted in previous versions. This new option enables workflows such as:
Getting a strict reference from a non-strict reference
Creating another reentrant instance of a reentrant VI
There are only two ways to tell somebody thanks: Kudos and Marked Solutions Unofficial Forum Rules and Guidelines "Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5