Symbolic path - Revision history

Felipefoz: /* External links */

2024-10-24T10:25:36Z

External links

← Older revision		Revision as of 10:25, 24 October 2024
Line 19:		Line 19:
	==External links==		==External links==
	*[https://lavag.org/topic/10549-resolving-symbolic-paths/ Resolving Symbolic Paths] (LAVA)		*[https://lavag.org/topic/10549-resolving-symbolic-paths/ Resolving Symbolic Paths] (LAVA)
			*[https://forums.ni.com/t5/Community-Documents/Resolution-of-Pseudopaths-in-LabVIEW-Per-Target-Invocation-of/ta-p/4087124 Resolution of Pseudopaths per Target] (NI forums)

	[[Category:Development Environment]]		[[Category:Development Environment]]

Logmanoriginal: Fix typos

2024-08-23T19:01:38Z

Fix typos

← Older revision		Revision as of 19:01, 23 August 2024
Line 1:		Line 1:
	A '''symbolic path''' (aka. ''pseudo path'') is a placeholder that represents one or more well-known locations in [[LabVIEW]]. When specifying a [[path]] to a file or folder inside a well-known location, rather than specifying the absolute path, the path is specified relative to the symbolic path. When accessing the path, it is resolved to the actual location, which may be different between machines, platforms, targets, and versions of LabVIEW.		A '''symbolic path''' (aka. ''pseudo path'') is a placeholder that represents one or more well-known locations in [[LabVIEW]]. When specifying a [[path]] to a file or folder inside a well-known location, rather than specifying the absolute path, the path is specified relative to the symbolic path. When accessing the path, it is resolved to the actual location, which may be different between machines, platforms, targets, and versions of LabVIEW.

	~~So a~~ [[VI]] that uses "<vilib>:\a.vi" may resolve to "<labview>\vi.lib\a.vi" when loaded for a desktop target, and "<labview>\vi.lib\fpga\a.vi" when loaded for a [[FPGA]] target.		A [[VI]] that uses "<vilib>:\a.vi" may resolve to "<labview>\vi.lib\a.vi" when loaded for a desktop target, and "<labview>\vi.lib\fpga\a.vi" when loaded for a [[FPGA]] target.

	A symbolic path can also refer to multiple locations that [[wikipedia:superimpose\|overlay]] each other as if they were a single directory. If a file with the same name exists in multiple directories, the first file found is used. The order in which directories are scanned may vary and can be determined using the [[Build And Resolve Symbolic Path]] VI with "symbolic path id" set to "<libdir>".		A symbolic path can also refer to multiple locations that [[wikipedia:superimpose\|overlay]] each other as if they were a single directory. If a file with the same name exists in multiple directories, the first file found is used. The order in which directories are scanned may vary and can be determined using the [[Build And Resolve Symbolic Path]] VI with "symbolic path id" set to "<libdir>".

	==Syntax==		==Syntax==
	Symbolic paths are used similar to drive letters in Windows. For example, "<userlib>:/myfile.txt" specifies a file named ''myfile.txt'' in the [[user.lib]] directory.		Symbolic paths are used similar to drive letters in Windows. For example, "<userlib>:\myfile.txt" specifies a file named ''myfile.txt'' in the [[user.lib]] directory.

	==Usage==		==Usage==
	LabVIEW uses symbolic paths internally to store ~~path~~ to files and folders. For example, the [[lvproj]] file format stores paths to files using symbolic paths. Symbolic paths are also useful for [[VI Scripting]].		LabVIEW uses symbolic paths internally to store paths to files and folders. For example, the [[lvproj]] file format stores paths to files using symbolic paths. Symbolic paths are also useful for [[VI Scripting]].

	==Resolving symbolic paths==		==Resolving symbolic paths==
	In order to access the actual path that a symbolic path represents, ~~the symbolic path~~ must be resolved. In [[LabVIEW 2023 Q3]] and later, the [[Build And Resolve Symbolic Path]] VI should be used. In earlier versions from [[LabVIEW 2015]] and later, the [[Resolve Symbolic Path (VI)\|Resolve Symbolic Path]] VI should be used. For even earlier versions, the private [[Resolve Symbolic Path (method)\|Resolve Symbolic Path]] method, which ~~was~~ deprecated in [[LabVIEW 8.5]], can be used.		In order to access the actual path that a symbolic path represents, it must be resolved. In [[LabVIEW 2023 Q3]] and later, the [[Build And Resolve Symbolic Path]] VI should be used. In earlier versions from [[LabVIEW 2015]] and later, the [[Resolve Symbolic Path (VI)\|Resolve Symbolic Path]] VI should be used. For even earlier versions, the private [[Resolve Symbolic Path (method)\|Resolve Symbolic Path]] method, which is deprecated since [[LabVIEW 8.5]], can be used.

	==See also==		==See also==

Logmanoriginal: Logmanoriginal moved page Symbolic Path to Symbolic path: Use standard naming conventions

2024-08-23T15:46:21Z

Logmanoriginal moved page Symbolic Path to Symbolic path: Use standard naming conventions

← Older revision	Revision as of 15:46, 23 August 2024
(No difference)

Logmanoriginal: Article rewrite, list of symbolic paths moved to separate page.

2024-08-23T15:45:59Z

Article rewrite, list of symbolic paths moved to separate page.

@@ Line 1: / Line 1: @@
-When files are located beneath certain special folders, callers that link to these files will link to them using a ''symbolic path'', rather than an absolute or relative path.  The ''symbolic path'' will be relative to the special folder.  The following table lists these special folders and their ''symbolic path'':
+A '''symbolic path''' (aka. ''pseudo path'') is a placeholder that represents one or more well-known locations in [[LabVIEW]]. When specifying a [[path]] to a file or folder inside a well-known location, rather than specifying the absolute path, the path is specified relative to the symbolic path. When accessing the path, it is resolved to the actual location, which may be different between machines, platforms, targets, and versions of LabVIEW.
-{| class="wikitable"
+So a [[VI]] that uses "<vilib>:\a.vi" may resolve to "<labview>\vi.lib\a.vi" when loaded for a desktop target, and "<labview>\vi.lib\fpga\a.vi" when loaded for a [[FPGA]] target.
-Note that some of these can have the actual path changed by changing the settings in '''Tools>>Options'''. The whole point of the symbolic path is to indicate "load from whatever location this path is currently defined to be."
+A symbolic path can also refer to multiple locations that [[wikipedia:superimpose|overlay]] each other as if they were a single directory. If a file with the same name exists in multiple directories, the first file found is used. The order in which directories are scanned may vary and can be determined using the [[Build And Resolve Symbolic Path]] VI with "symbolic path id" set to "<libdir>".
-For example, if you have a VI located in the following location:
+==Syntax==
-<LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
+==Usage==
-Callers will link to this VI using the following ''symbolic path'':
+==Resolving symbolic paths==
-<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi
+==See also==
-''symbolic path'' 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.
+==External links==
 [[Category:Development Environment]]

Jim kring: /* Resolving Symbolic Paths Programmatically */

2022-09-05T20:02:52Z

Resolving Symbolic Paths Programmatically

← Older revision		Revision as of 20:02, 5 September 2022
Line 54:		Line 54:

	[[Image:ResolveSymbolicPath.png]]		[[Image:ResolveSymbolicPath.png]]

			Note: That the 'Resolve Symbolic Path' Application Method is only visible if you have set [[LabVIEW_configuration_file/Miscellaneous#SuperSecretPrivateSpecialStuff\|SuperSecretPrivateSpecialStuff]]=True in your [[LabVIEW_configuration_file\|LabVIEW configuration file]].

	== Auto update of symbolic paths ==		== Auto update of symbolic paths ==

Hooovahh at 17:40, 18 April 2022

2022-04-18T17:40:56Z

← Older revision		Revision as of 17:40, 18 April 2022
Line 19:		Line 19:
	\| <LabVIEW>\instr.lib		\| <LabVIEW>\instr.lib
	\|-		\|-
	\| <~~help~~>		\| <helpdir>
	\| Help Files		\| Help Files
	\| <LabVIEW>\help		\| <LabVIEW>\help

Jim kring: Added the "resource" symbolic path.

2021-01-23T22:58:33Z

Added the "resource" symbolic path.

← Older revision		Revision as of 22:58, 23 January 2021
Line 30:		Line 30:
	\| Palette Menus		\| Palette Menus
	\| <LabVIEW>\menus		\| <LabVIEW>\menus
			\|-
			\| <resource>
			\| Various VIs and resources used by LabVIEW and plugins, and generally not intended to be called by end-user applications.
			''Note this first appeared in LabVIEW 2012 (based on [https://forums.ni.com/t5/Developer-Center-Discussions/Make-the-LabVIEW-quot-resource-quot-folder-a-symbolic-path/td-p/3438293?profile.language=en this idea exchange post]) and prior to that it was not a symbolic path.''
			\| <LabVIEW>\resource
	\|}		\|}

Logmanoriginal: Fix category assignment

2020-04-10T10:01:31Z

Fix category assignment

← Older revision		Revision as of 10:01, 10 April 2020
Line 69:		Line 69:
	* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/using_symbolic_paths/ LabVIEW Help: Using Symbolic Paths]		* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/using_symbolic_paths/ LabVIEW Help: Using Symbolic Paths]

	[[~~category~~:~~development environment~~]]		[[Category:File IO]]
	[[~~category~~:~~File IO~~]]		[[Category:Development Environment]]

MichaelAivaliotis: /* Resolving Symbolic Paths Programmatically */

2009-07-22T06:27:18Z

Resolving Symbolic Paths Programmatically

← Older revision		Revision as of 06:27, 22 July 2009
Line 49:		Line 49:

	[[Image:ResolveSymbolicPath.png]]		[[Image:ResolveSymbolicPath.png]]

	~~You can download a VI with this deprecated method, here: [http://forums.lavag.org/post-a10538-ResolveSymbolicPath.vi ResolveSymbolicPath.vi]~~

	== Auto update of symbolic paths ==		== Auto update of symbolic paths ==

Tcplomp: /* Resolving Symbolic Paths Programmatically */ Red means deprecated, not private

2009-01-19T22:00:35Z

Resolving Symbolic Paths Programmatically: Red means deprecated, not private

← Older revision		Revision as of 22:00, 19 January 2009
Line 50:		Line 50:
	[[Image:ResolveSymbolicPath.png]]		[[Image:ResolveSymbolicPath.png]]

	You can download a VI with this ~~private~~ method, here: [http://forums.lavag.org/post-a10538-ResolveSymbolicPath.vi ResolveSymbolicPath.vi]		You can download a VI with this deprecated method, here: [http://forums.lavag.org/post-a10538-ResolveSymbolicPath.vi ResolveSymbolicPath.vi]

	== Auto update of symbolic paths ==		== Auto update of symbolic paths ==