LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

relative paths decent examples

 
 
Can anyone point me to some decent examples of using relative paths?
I've done some searching and found a little bit but need more clarification.
I learn best by looking at good examples.
 
I want to insure my built APP can find what it needs regardless of what directory it is installed into.
 
Thank you.
 
TG
 
 
0 Kudos
Message 1 of 4
(2,722 Views)

I believe that the KnowledgeBase article linked below will be very helpful.  It does not include an example, but it includes an image of a block diagram that could be added to your VI.  Please let me know if this is what you are looking for.

Accessing a VI's Current Directory From LabVIEW and a Stand-Alone Application

Meghan M.

0 Kudos
Message 2 of 4
(2,694 Views)

Yes thank you for that article and yes it is helpful.

I am also interested in any "tricks of the trade"  along these lines.

For example My APP is fairly large and I want to make sure that it can find the files and VI's it needs when it is compiled.

I d rather use relative paths to insure that there is no hardcoded path information in the exe which could

throw things off. For example should someone decide to install the executable in a different directory than the intended

"..\APPNAME" the application should be able to sort it out and find what it needs in the subfolders and should be able to do this

in edit mode or executable. I am looking for any techniques and examples along those lines that would make robust and generic handling of paths to the needed resources.

Thank You

 

 

0 Kudos
Message 3 of 4
(2,677 Views)
If you are worried about VI locations when compiling your executable, as long as they are included in the "Always Included" seciton of your exectuable configuration, you should not run into any problems.  If you are using a Current VI's Path Constant in your executable, please read the following KnowledgeBase.  Thanks!
 
 
Meghan M.
0 Kudos
Message 4 of 4
(2,646 Views)