Symbolic path: Difference between revisions

Revision as of 20:14, 4 May 2007

When files are located beneath the following special folders:

description	path
User Libraries	<LabVIEW>\user.lib
NI Libraries and Addons	<LabVIEW>\vi.lib
Instrument Drivers	<LabVIEW>\instr.lib

Callers that link to these files will link to them using a psuedopath, rather than an absolute or relative path. The psuedopath will be relative to the special folder:

For example, if you have a VI located in the following location:

<LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi

Callers will link to this VI using the following pseudopath:

<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi

The following are valid pseudopaths:

pseudopath	path
<userlib>	<LabVIEW>\user.lib
<vilib>	<LabVIEW>\vi.lib
<instrlib>	<LabVIEW>\instr.lib

Pseudopaths are not generally encountered. They are used mostly under the hood of LabVIEW, for example, when using the Application Linker:Read Info From File and Linker:Write Info To File methods.

@@ Line 22: / Line 22: @@
 <LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
-Callers will link to this VI using the following ''psuedopath'':
+Callers will link to this VI using the following ''pseudopath'':
 <userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
-The following are valid ''psuedopaths'':
+The following are valid ''pseudopaths'':
 {| class="wikitable"
 |-
-! psuedopath
+! pseudopath
 ! path
 |-
@@ Line 43: / Line 43: @@
 |}
-''Psuedopaths'' are not generally encountered.  They are used mostly under the hood of LabVIEW, for example, when using the Application '''Linker:Read Info From File''' and '''Linker:Write Info To File''' methods.
+''Pseudopaths'' are not generally encountered.  They are used mostly under the hood of LabVIEW, for example, when using the Application '''Linker:Read Info From File''' and '''Linker:Write Info To File''' methods.