Symbolic path: Difference between revisions
New page: When files are located beneath the following special folders: {| class="wikitable" |- ! description ! path |- | User Libraries | <LabVIEW>\user.lib |- | NI Libraries and Addons | <LabVIEW... |
added example of psuedopaths used in Application "Linker" methods |
||
| Line 42: | Line 42: | ||
| <LabVIEW>\instr.lib | | <LabVIEW>\instr.lib | ||
|} | |} | ||
''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. | |||
Revision as of 19:00, 2 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 psuedopath:
<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
The following are valid psuedopaths:
| psuedopath | path |
|---|---|
| <userlib> | <LabVIEW>\user.lib |
| <vilib> | <LabVIEW>\vi.lib |
| <instrlib> | <LabVIEW>\instr.lib |
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.