Re: Current VI's Path

[Jim K. <jk...@ja...>]

Derrick,

As Rolf mentioned, the OpenG version of "Current VIs Path.vi" behaves 
just like LabVIEW native (primitive) function "Current VIs Path", which 
is found in the File Constants palette.  The one improvement of the 
OpenG version is that you can pass in a relative path -- in your case 
you could pass in a ".." to produce the path to the folder (or LLB) 
containing the VI.  You will also notice several other File Constants on 
the OpenG palette which are found in the primitive File Constants 
palette.  All these have behavior that is defined by the primitives.

Thanks for posting your modified version.  We welcome participation!

Regards,

-Jim


Swinarsky, DJ Derrick (5453) @ IS wrote:

>If that is the desired output, then I will go along with it.  
>
>Derrick
>
>p.s.  Sorry for posting the modified version to the mailing list.  After I
>sent the email I thought that it might not have been a smart idea...
>
>-----Original Message-----
>From: Rolf Kalbermatter [mailto:rol...@ci...]
>Sent: Friday, April 16, 2004 11:10 AM
>To: ope...@li...
>Subject: RE: Current VI's Path
>
>
>Swinarsky, DJ Derrick (5453) @ IS wrote:
>
>  
>
>>I believe there may be an error within Current VI's Path... 
>>or just don't understand why it works as it does.
>>    
>>
>
>Well, this is about what is the definition of a path. For some
>a path is just the entire absolute path to a file or directory,
>for others it is the absolute path to the directory a file is
>in. I personally tend to the first category.
>Some use filename to indicate the entire path to a file and
>others mean with filename only the last component in a path. 
>
>What is right and what is wrong? I guess nobody and anybody!
>Microsoft itself is not consistent in its MSDN API documentation
>for the Win32 API in this and so are most other API documentations.
>
>At least in the LabVIEW documentation a path is just a specific
>datatype which can be absolute, relative, or invalid and can point
>to a volume, directory or file. The constant returning the path of
>the Current VI uses the same convention as is used in the original
>OpenG VI.
>
>Rolf Kalbermatter
>
>  
>