RE: Current VI's Path

[Swinarsky, DJ D. (5. @ I. <d.s...@L-...>]

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



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
OpenGToolkit-Developers mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers