VI Server - Revision history

Flarn2006: /* Deprecated */ Add info on how to show deprecated properties/methods in the menu

2022-01-22T19:06:25Z

Deprecated: Add info on how to show deprecated properties/methods in the menu

← Older revision		Revision as of 19:06, 22 January 2022
Line 45:		Line 45:
	=== Deprecated ===		=== Deprecated ===
	[[File:VI Server Deprecated.png\|thumb\|413x413px\|Deprecated VI Server Call and Its Replacement]]		[[File:VI Server Deprecated.png\|thumb\|413x413px\|Deprecated VI Server Call and Its Replacement]]
	From time-to-time, G is modified to give more features or to regroup functionality. In these cases the old version of properties and methods could be taken out of use, or deprecated. These features are never fully removed, to keep from breaking older programs, but they are no longer discoverable in Property Nodes or Invoke Nodes.		From time-to-time, G is modified to give more features or to regroup functionality. In these cases the old version of properties and methods could be taken out of use, or deprecated. These features are never fully removed, to keep from breaking older programs, but they are no longer discoverable in Property Nodes or Invoke Nodes. This can be overridden by turning on "ObjectManager.ShowDeprecated" in the [[Ned options]], allowing deprecated properties and methods to be selected from the menu, but there is little to no reason to do so.

	== Articles ==		== Articles ==

Q: Added VI Scripting Category to page

2020-05-08T01:14:51Z

Added VI Scripting Category to page

← Older revision		Revision as of 01:14, 8 May 2020
Line 56:		Line 56:

	[[Category:Application Control]]		[[Category:Application Control]]
	~~[[Category:VI Scripting]]~~
	[[Category:VI Server]]		[[Category:VI Server]]

Q: Category reorg

2020-05-07T13:49:42Z

Category reorg

← Older revision		Revision as of 13:49, 7 May 2020
Line 57:		Line 57:
	[[Category:Application Control]]		[[Category:Application Control]]
	[[Category:VI Scripting]]		[[Category:VI Scripting]]
	~~[[Category:Properties]]~~
	~~[[Category:Methods]]~~
	~~[[Category:Events (Event Structure)]]~~
	[[Category:VI Server]]		[[Category:VI Server]]

Q: /* Private */ Combining content from a duplicate page

2020-05-07T13:48:56Z

Private: Combining content from a duplicate page

← Older revision		Revision as of 13:48, 7 May 2020
Line 37:		Line 37:
	=== Private ===		=== Private ===
	[[File:VI Server Private.png\|thumb\|388x388px\|Private VI Server Calls]]		[[File:VI Server Private.png\|thumb\|388x388px\|Private VI Server Calls]]
	This adds more lower level control and functionality. There is a reason they are private. They are not always fully vetted or documented. They also could change from one version of LabVIEW to the next and they might not be in the LabVIEW Run-Time Engine, (meaning they cannot be used in built executable). Use at your own risk.		'''This adds more, lower level control and functionality. There is a reason they are private. They are not always fully vetted or documented. They also could change from one version of LabVIEW to the next and they might not be in the LabVIEW Run-Time Engine, (meaning they cannot be used in built executable). Use at your own risk.'''

	When the private functions are enabled the Class Specifier Constant, Property Nodes, and Invoke Nodes turn brown when containing private Classes, Properties and Methods, respectively. If private functions are being used but then the functionality is disabled, they will continue to work but they will appear either the standard yellow, or if scripting is turned on they might appear light cyan, and they will no longer be discoverable.		When the private functions are enabled the Class Specifier Constant, Property Nodes, and Invoke Nodes turn brown when containing private Classes, Properties and Methods, respectively. If private functions are being used but then the functionality is disabled, they will continue to work but they will appear either the standard yellow, or if scripting is turned on they might appear light cyan, and they will no longer be discoverable.

	~~See more on [[~~Private methods and ~~properties~~]].		To expose the Private classes, methods, properties, and events edit your [[LabVIEW configuration file]] to include the ''SuperSecretPrivateSpecialStuff=True'' setting. You can search the LAVA forums for the tag Private method for additional events and use cases.

	=== Deprecated ===		=== Deprecated ===

Q: Category reorg

2020-05-07T12:12:01Z

Category reorg

← Older revision		Revision as of 12:12, 7 May 2020
Line 59:		Line 59:
	[[Category:Properties]]		[[Category:Properties]]
	[[Category:Methods]]		[[Category:Methods]]
	[[Category:Events]]		[[Category:Events (Event Structure)]]
	[[Category:VI Server]]		[[Category:VI Server]]

Q: /* Deprecated */ typo

2019-08-27T01:17:04Z

Deprecated: typo

← Older revision		Revision as of 01:17, 27 August 2019
Line 45:		Line 45:
	=== Deprecated ===		=== Deprecated ===
	[[File:VI Server Deprecated.png\|thumb\|413x413px\|Deprecated VI Server Call and Its Replacement]]		[[File:VI Server Deprecated.png\|thumb\|413x413px\|Deprecated VI Server Call and Its Replacement]]
	From time-to-time, G is modified to give more features or to regroup functionality. In these cases the old version of properties and methods could be taken out of use, or deprecated. These features are never fully removed, to keep from breaking older programs, but they are no ~~long~~ discoverable in Property Nodes or Invoke Nodes.		From time-to-time, G is modified to give more features or to regroup functionality. In these cases the old version of properties and methods could be taken out of use, or deprecated. These features are never fully removed, to keep from breaking older programs, but they are no longer discoverable in Property Nodes or Invoke Nodes.

	== Articles ==		== Articles ==

Q at 16:11, 18 August 2019

2019-08-18T16:11:00Z

← Older revision		Revision as of 16:11, 18 August 2019
Line 2:		Line 2:
	'''VI Server''', introduced in LabVIEW 5.0, is a set of functions that allows you to dynamically control front panel objects, VIs, and the LabVIEW environment. With VI Server, you can also programmatically load and run VIs and LabVIEW either on the same machine or across a network. The VI Server functions are located in the '''Functions » Application''' Control sub-palette. All VIs have properties that can be read or set and methods that can be invoked using these VI Server functions. VI Server replaces the VI Control VIs of LabVIEW 4.x.		'''VI Server''', introduced in LabVIEW 5.0, is a set of functions that allows you to dynamically control front panel objects, VIs, and the LabVIEW environment. With VI Server, you can also programmatically load and run VIs and LabVIEW either on the same machine or across a network. The VI Server functions are located in the '''Functions » Application''' Control sub-palette. All VIs have properties that can be read or set and methods that can be invoked using these VI Server functions. VI Server replaces the VI Control VIs of LabVIEW 4.x.

	VI Server has an object-oriented architecture that is platform-independent. Each object that is a part of VI Server is a part of a class. The class that the object is a part of determines what properties and methods are available. Many of these classes have sub-classes. For instance, any boolean control is a member of the Boolean class, which is a member of the Control class. The Control class is a member of the GObject class, which is a member of the Generic class. Lower level classes, such as the Boolean class, have their own properties and methods, and inherit properties and methods from higher level classes, such as the Generic class.		VI Server has an object-oriented architecture that is platform-independent, (see [[VI Server Class Hierarchy]]). Each object that is a part of VI Server is a part of a class. The class that the object is a part of determines what properties and methods are available. Many of these classes have sub-classes. For instance, any boolean control is a member of the Boolean class, which is a member of the Control class. The Control class is a member of the GObject class, which is a member of the Generic class. Lower level classes, such as the Boolean class, have their own properties and methods, and inherit properties and methods from higher level classes, such as the Generic class.

	In order to create a VI Server session, one has to open an [[Application Reference]] to remote computers and a [[VI Reference]] [VI-Ref] on the desired computer.		In order to create a VI Server session, one has to open an [[Application Reference]] to remote computers and a [[VI Reference]] [VI-Ref] on the desired computer.
	With that VI-Ref one can perform actions with the VI like setting or retrieving control values, running it or setting and retrieving the VIs properties.		With that VI-Ref one can perform actions with the VI like setting or retrieving control values, running it or setting and retrieving the VIs properties.

	~~== VI Server Class Hierarchy ==~~

	~~The full VI Server Class Hierarchy can be viewed here:~~

	~~[http://zone.ni.com/reference/en-XX/help/371361R-01/lvprop/propmeth_class_hierarchy/ VI Server Class Hierarchy from the LabVIEW Help Page]~~

	== VI Server Levels ==		== VI Server Levels ==

Dnatt at 20:27, 31 May 2019

2019-05-31T20:27:21Z

← Older revision		Revision as of 20:27, 31 May 2019
Line 21:		Line 21:
	* Panes and Panels		* Panes and Panels
	* VIs		* VIs
	* Projects, Libraries, and Classes		* [[ProjectItem]] (Projects, Libraries, and Classes)
	* Application		* Application
	The standard color of Class Specifier Constant, Property Nodes, and Invoke Nodes is yellow when they do not contain any scripting, private, or deprecated Classes, Properties or Methods, respectively. As soon as one of the others appear in the Property Node or Invoke Node the color will change according to the following order of importance:		The standard color of Class Specifier Constant, Property Nodes, and Invoke Nodes is yellow when they do not contain any scripting, private, or deprecated Classes, Properties or Methods, respectively. As soon as one of the others appear in the Property Node or Invoke Node the color will change according to the following order of importance:

Q at 05:39, 12 November 2018

2018-11-12T05:39:42Z

← Older revision		Revision as of 05:39, 12 November 2018
Line 3:		Line 3:

	VI Server has an object-oriented architecture that is platform-independent. Each object that is a part of VI Server is a part of a class. The class that the object is a part of determines what properties and methods are available. Many of these classes have sub-classes. For instance, any boolean control is a member of the Boolean class, which is a member of the Control class. The Control class is a member of the GObject class, which is a member of the Generic class. Lower level classes, such as the Boolean class, have their own properties and methods, and inherit properties and methods from higher level classes, such as the Generic class.		VI Server has an object-oriented architecture that is platform-independent. Each object that is a part of VI Server is a part of a class. The class that the object is a part of determines what properties and methods are available. Many of these classes have sub-classes. For instance, any boolean control is a member of the Boolean class, which is a member of the Control class. The Control class is a member of the GObject class, which is a member of the Generic class. Lower level classes, such as the Boolean class, have their own properties and methods, and inherit properties and methods from higher level classes, such as the Generic class.

			In order to create a VI Server session, one has to open an [[Application Reference]] to remote computers and a [[VI Reference]] [VI-Ref] on the desired computer.
			With that VI-Ref one can perform actions with the VI like setting or retrieving control values, running it or setting and retrieving the VIs properties.

			== VI Server Class Hierarchy ==

	The full VI Server Class Hierarchy can be viewed here:		The full VI Server Class Hierarchy can be viewed here:

	[http://zone.ni.com/reference/en-XX/help/371361R-01/lvprop/propmeth_class_hierarchy/ VI Server Class Hierarchy from the LabVIEW Help Page]		[http://zone.ni.com/reference/en-XX/help/371361R-01/lvprop/propmeth_class_hierarchy/ VI Server Class Hierarchy from the LabVIEW Help Page]

	~~In order to create a VI Server session, one has to open an [[Application Reference]] to remote computers and a [[VI Reference]] [VI-Ref] on the desired computer.~~
	~~With that VI-Ref one can perform actions with the VI like setting or retrieving control values, running it or setting and retrieving the VIs properties.~~

	== VI Server Levels ==		== VI Server Levels ==
Line 60:		Line 62:

	[[Category:Application Control]]		[[Category:Application Control]]
	~~[[Category:VI Scripting]]~~
	~~[[Category:Properties]]~~
	~~[[Category:Methods]]~~
	~~[[Category:Events]]~~
	~~[[Category:VI Server]]~~
	[[Category:VI Scripting]]		[[Category:VI Scripting]]
	[[Category:Properties]]		[[Category:Properties]]

Q: /* Private */ Adding link to internal page

2018-11-11T04:13:04Z

Private: Adding link to internal page

← Older revision		Revision as of 04:13, 11 November 2018
Line 44:		Line 44:

	When the private functions are enabled the Class Specifier Constant, Property Nodes, and Invoke Nodes turn brown when containing private Classes, Properties and Methods, respectively. If private functions are being used but then the functionality is disabled, they will continue to work but they will appear either the standard yellow, or if scripting is turned on they might appear light cyan, and they will no longer be discoverable.		When the private functions are enabled the Class Specifier Constant, Property Nodes, and Invoke Nodes turn brown when containing private Classes, Properties and Methods, respectively. If private functions are being used but then the functionality is disabled, they will continue to work but they will appear either the standard yellow, or if scripting is turned on they might appear light cyan, and they will no longer be discoverable.

			See more on [[Private methods and properties]].

	=== Deprecated ===		=== Deprecated ===