Symbolic path: Difference between revisions
added help and menu pseudopaths and merged the two tables. |
m Pseudopath moved to Symbolic Path: LabVIEW calls these "Symbolic Paths" -- see here: http://forums.lavag.org/index.php?s=&showtopic=7790&view=findpost&p=29512 |
(No difference)
| |
Revision as of 20:30, 7 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.