Jump to content

Symbolic path: Difference between revisions

From LabVIEW Wiki
m spelling - changed "psuedopath" to "pseudopath"
added help and menu pseudopaths and merged the two tables.
Line 1: Line 1:
When files are located beneath the following special folders:
When files are located beneath certain special folders, callers that link to these files will link to them using a ''pseudopath'', rather than an absolute or relative path.  The ''pseudopath'' will be relative to the special folder.  The following table lists these special folders and their ''pseudopath'':


{| class="wikitable"
{| class="wikitable"
|-
|-
! pseudopath
! description
! description
! path
! actual path
|-
|-
| <userlib>
| User Libraries
| User Libraries
| <LabVIEW>\user.lib
| <LabVIEW>\user.lib
|-
|-
| <vilib>
| NI Libraries and Addons
| NI Libraries and Addons
| <LabVIEW>\vi.lib
| <LabVIEW>\vi.lib
|-
|-
| <instrlib>
| Instrument Drivers
| Instrument Drivers
| <LabVIEW>\instr.lib
| <LabVIEW>\instr.lib
|-
| <help>
| Help Files
| <LabVIEW>\help
|-
| <menu>
| Palette Menus
| <LabVIEW>\menus
|}
|}
Callers that link to these files will link to them using a ''pseudopath'', rather than an absolute or relative path.  The ''pseudopath'' will be relative to the special folder:


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


<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
The following are valid ''pseudopaths'':
{| class="wikitable"
|-
! 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.
''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.

Revision as of 20:26, 5 May 2007

When files are located beneath certain special folders, callers that link to these files will link to them using a pseudopath, rather than an absolute or relative path. The pseudopath will be relative to the special folder. The following table lists these special folders and their pseudopath:

pseudopath description actual path
<userlib> User Libraries <LabVIEW>\user.lib
<vilib> NI Libraries and Addons <LabVIEW>\vi.lib
<instrlib> Instrument Drivers <LabVIEW>\instr.lib
<help> Help Files <LabVIEW>\help
<menu> Palette Menus <LabVIEW>\menus

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

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.