Open VI Reference fx - VI Path input should have default value of 'Current VI's Path'

[DonRoth]

The value for VI Path input for Open VI Reference fx might be the most commonly used option - therefore, why not have it as default when placing it on the diagram?  Currently, broken arrow occurs when placing this function on the block diagram.

[tst]

---

@DonRoth wrote:

...why not have it as default when placing it on the diagram?

---

Because it's completely unneeded - if you're getting a reference to the current VI, you're going to use it with property or invoke nodes and there are already two shortcuts for that:

1. There's a This VI reference in the app control palette.
2. If you select the VI class in a property or invoke node and don't wire a reference in, it operates on the current VI. The same thing applies to the Application class.

The only time I use the OVR primitive is to open a reference to another VI.

[DonRoth]

Valid and excellent points.  However, some redundancy here is not a bad thing.

[tst]

> ...some redundancy here is not a bad thing.

Perhaps not (some may argue that it is), but I prefer my code to break if I didn't handle something I need to handle, and this qualifies.

[MaryH]

Primary use case for this node is to get a reference for other VIs and breaking the caller when the path is unwired is a key part of making sure a diagram is wired correctly.

[DonRoth]

Always was a fan of those who could make quick decisions