Improved Current VI's Path

[JB]

Most of us have developped our own VI to handle the difference of a VI's path when in development and EXE. See here for an example.

The numerous pages on ni.com and questions on the forums about this topic show the need for an improved native Current VI's Path function.

[tst]

It's not impossible that NI is already working on such a feature.

[Ray.R]

Such a feature would be very helpful to novice users of LabVIEW.

No more need for "development vs deployed" current vi path function.   🙂

[Darren]

Is the Application Directory VI (added in LabVIEW 2009) a suitable implementation for this idea? If so, I'll close out the idea as Completed.

[GB1984_]

Yes, the "Application Directory" VI is a suitable implementation.

It does eliminate the need to implement a complicated mechanism to recognize whether the application is running within the LabVIEW IDE or as a compiled executable, as is the case with the "Current VI's Path" function.

It is regrettable that as recently as in LabVIEW 2014, five years after the introduction of "Application Directory" in LV2009, there is no reference to the "Application Directory" VI on the help page for "Current VI's Path", not even a "See also" section for similar functions.

One has to go through the arduous process of debugging, inventing countermeasures, trying to provide feedback, ending up on a discussion forum, and finally discovering a different and trivial solution. All of that taking several hours, just because in the beginning of time "Current VI's Path" had a bug that was later explained away on its help page as a "design feature".

[Darren]

I have filed CAR 513627 to update the help for the Current VI's Path function to reference the Application Directory VI.

[Darren]

Functionality is available with the Application Directory VI (LabVIEW 2009 and later)