XControl - Revision history

Q at 15:58, 9 June 2020

2020-06-09T15:58:09Z

← Older revision		Revision as of 15:58, 9 June 2020
Line 13:		Line 13:
	Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.		Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.

	Also, XControls have limitations when running in VIs that are part of a [[~~Library~~ Project Library]] (or [[Packed Project Library\|Packed Project Library (PPL)]]), or a [[LabVIEW Class]]. This makes it difficult to use in a large application using [[Actor Framework]] or plugin architectures using [[Packed Project Library\|PPLs]]. See more in the [[QControl\|QControls]] article.		Also, XControls have limitations when running in VIs that are part of a [[LabVIEW Project Library]] (or [[Packed Project Library\|Packed Project Library (PPL)]]), or a [[LabVIEW Class]]. This makes it difficult to use in a large application using [[Actor Framework]] or plugin architectures using [[Packed Project Library\|PPLs]]. See more in the [[QControl\|QControls]] article.

	== Tricks ==		== Tricks ==

Q at 15:57, 9 June 2020

2020-06-09T15:57:53Z

← Older revision		Revision as of 15:57, 9 June 2020
Line 13:		Line 13:
	Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.		Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.

	Also, XControls have limitations when running in VIs that are part of a [[Library]] (or [[Packed Project Library\|Packed Project Library (PPL)]]), or a [[LabVIEW Class]]. This makes it difficult to use in a large application using [[Actor Framework]] or plugin architectures using [[Packed Project Library\|PPLs]]. See more in the [[QControl\|QControls]] article.		Also, XControls have limitations when running in VIs that are part of a [[Library Project Library]] (or [[Packed Project Library\|Packed Project Library (PPL)]]), or a [[LabVIEW Class]]. This makes it difficult to use in a large application using [[Actor Framework]] or plugin architectures using [[Packed Project Library\|PPLs]]. See more in the [[QControl\|QControls]] article.

	== Tricks ==		== Tricks ==

Q: Updated links

2020-06-08T16:01:38Z

Updated links

← Older revision		Revision as of 16:01, 8 June 2020
Line 1:		Line 1:
	'''XControls''' were first introduced in [[LabVIEW 8]] and enhance the power of front panel objects. An XControl is a front panel object with dedicated UI logic code linked and ~~encapsulatedin~~ the XControl in order to react to user events on the controls in contains. An XControl consists of several parts, managed in a ''.xctl'' file. The ''.xctl'' file is a XML-file like ~~the project-file~~ or [[Library]] files. Other parts of the XControl are called:		{{TOCright}}'''XControls''' were first introduced in [[LabVIEW 8]] and enhance the power of front panel objects. An XControl is a front panel object with a dedicated UI logic code linked and encapsulated in the XControl in order to react to user events on the controls it contains. An XControl consists of several parts, managed in a [[XCTL File Extension \|''.xctl'']] file. The ''.xctl'' file is a XML file like similar to [[LabVIEW Project]] or [[LabVIEW Project Library]] files.

			Other parts of the XControl are called:
	*[[XControl:Properties\|Properties]]		*[[XControl:Properties\|Properties]]
	*[[XControl:Abilities\|Abilities]]		*[[XControl:Abilities\|Abilities]]
	*[[XControl:Methods\|Methods]]		*[[XControl:Methods\|Methods]]

	~~__TOC__~~

	== Limitations ==		== Limitations ==
	An XControl functions like a subpanel in the hosting VI. ~~Subpanels~~ (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.		An XControl functions like a subpanel in the hosting VI. [[Subpanel]]s (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.

	Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.		Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.
Line 18:		Line 20:
	* If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.		* If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.
	* If Façade is not executing fast enough to keep up with data updates, it causes the updates to queue up. The updates will happen even after the VI stops running. To reduce data updates:		* If Façade is not executing fast enough to keep up with data updates, it causes the updates to queue up. The updates will happen even after the VI stops running. To reduce data updates:
	Thanks to Ram Kudukoli (of NI R&D) for sharing this with us at the recent CLA Summit:		: (Thanks to Ram Kudukoli (of NI R&D) for sharing this with us at the recent CLA Summit)
			:* Open the Xcontrol .xctl file in a text editor like Notepad.
	** Open the Xcontrol .xctl file in a text editor like Notepad.		:* Add the bolded line shown below:
	** Add the bolded line shown below:
	<Property Name="NI.Lib.Version" Type="Str">1.0.0.0</Property>		<Property Name="NI.Lib.Version" Type="Str">1.0.0.0</Property>
	<Property Name="NI.XClass.Flags" Type="Int">0</Property>		<Property Name="NI.XClass.Flags" Type="Int">0</Property>
	'''<Property Name="NI.XCtl.OptimizeDataUpdate" Type="Bool">true</Property>		'''<Property Name="NI.XCtl.OptimizeDataUpdate" Type="Bool">true</Property>
	<Property Name="NI.XItem.DeclaredLeakProof" Type="Bool">false</Property>'''		<Property Name="NI.XItem.DeclaredLeakProof" Type="Bool">false</Property>'''
	** Save the .xctl file.		:* Save the .xctl file.
	([http://lavag.org/topic/15680-no-update-on-x-control-value-change/page__view__findpost__p__94838 LAVAG source])		([http://lavag.org/topic/15680-no-update-on-x-control-value-change/page__view__findpost__p__94838 LAVAG source])

Smercer: /* Tricks */

2020-04-05T04:40:51Z

Tricks

← Older revision		Revision as of 04:40, 5 April 2020
Line 24:		Line 24:
	<Property Name="NI.Lib.Version" Type="Str">1.0.0.0</Property>		<Property Name="NI.Lib.Version" Type="Str">1.0.0.0</Property>
	<Property Name="NI.XClass.Flags" Type="Int">0</Property>		<Property Name="NI.XClass.Flags" Type="Int">0</Property>
	<Property Name="NI.XCtl.OptimizeDataUpdate" Type="Bool">true</Property>		'''<Property Name="NI.XCtl.OptimizeDataUpdate" Type="Bool">true</Property>
	<Property Name="NI.XItem.DeclaredLeakProof" Type="Bool">false</Property>		<Property Name="NI.XItem.DeclaredLeakProof" Type="Bool">false</Property>'''
	** Save the .xctl file.		** Save the .xctl file.
	([http://lavag.org/topic/15680-no-update-on-x-control-value-change/page__view__findpost__p__94838 LAVAG source])		([http://lavag.org/topic/15680-no-update-on-x-control-value-change/page__view__findpost__p__94838 LAVAG source])

Q: Reorganized page and added more detail.

2018-12-01T04:47:52Z

Reorganized page and added more detail.

← Older revision		Revision as of 04:47, 1 December 2018
Line 1:		Line 1:
	~~__NOTOC__~~		'''XControls''' were first introduced in [[LabVIEW 8]] and enhance the power of front panel objects. An XControl is a front panel object with dedicated UI logic code linked and encapsulatedin the XControl in order to react to user events on the controls in contains. An XControl consists of several parts, managed in a ''.xctl'' file. The ''.xctl'' file is a XML-file like the project-file or [[Library]] files. Other parts of the XControl are called:
			*[[XControl:Properties\|Properties]]
	~~{\| border="0" align="right"~~		*[[XControl:Abilities\|Abilities]]
	\|-		*[[XControl:Methods\|Methods]]
	~~\| __TOC__~~
	\|}

	~~== Introduction ==~~
	XControls ~~are~~ introduced in LabVIEW 8.0 and enhance the power of front panel objects ~~in great ways~~.

	~~Essentially an~~ XControl is a front panel object with dedicated code linked in to react ~~on certain~~ user events.

	~~An XControl exists of several parts, managed in a .xctl file. The .xctl file is a XML-file like the project-file. Other parts of the XControl are abilities.~~		__TOC__

	== Limitations ==		== Limitations ==
	An XControl functions like a subpanel in the hosting VI. Subpanels (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.		An XControl functions like a subpanel in the hosting VI. Subpanels (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.

	Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.		Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.

			Also, XControls have limitations when running in VIs that are part of a [[Library]] (or [[Packed Project Library\|Packed Project Library (PPL)]]), or a [[LabVIEW Class]]. This makes it difficult to use in a large application using [[Actor Framework]] or plugin architectures using [[Packed Project Library\|PPLs]]. See more in the [[QControl\|QControls]] article.

	== Tricks ==		== Tricks ==
	*If you require a variable number of runtime instances of your XControl, Jarrod Slocum of [[National Instruments]] has created an example [http://community.ni.com/examples/linked-object-list-in-labview-8-0-using-xcontrols Linked Object List] based on a Subpanel ''inside'' an XControl.		*If you require a variable number of runtime instances of your XControl, Jarrod Slocum of [[National Instruments]] has created an example [http://community.ni.com/examples/linked-object-list-in-labview-8-0-using-xcontrols Linked Object List] based on a Subpanel ''inside'' an XControl.

	*If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.		* If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.
	* If Façade is not executing fast enough to keep up with data updates, it causes the updates to queue up. The updates will happen even after the VI stops running. To reduce data updates:		* If Façade is not executing fast enough to keep up with data updates, it causes the updates to queue up. The updates will happen even after the VI stops running. To reduce data updates:
	Thanks to Ram Kudukoli (of NI R&D) for sharing this with us at the recent CLA Summit:		Thanks to Ram Kudukoli (of NI R&D) for sharing this with us at the recent CLA Summit:
Line 35:		Line 30:

	== See also ==		== See also ==
	*[[XControl:Properties\|Properties]]
	*[[XControl:Abilities\|Abilities]]
	*[[XControl:Methods\|Methods]]
	*[[QControl\|QControls]]		*[[QControl\|QControls]]

	[[Category:XControl]]		[[Category:XControl]]

Q: /* See also */

2018-12-01T04:34:50Z

Tcplomp: Added OptimizeDataUpdate

2012-04-21T08:12:34Z

Added OptimizeDataUpdate

← Older revision		Revision as of 08:12, 21 April 2012
Line 22:		Line 22:

	*If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.		*If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.
			* If Façade is not executing fast enough to keep up with data updates, it causes the updates to queue up. The updates will happen even after the VI stops running. To reduce data updates:
			Thanks to Ram Kudukoli (of NI R&D) for sharing this with us at the recent CLA Summit:

			** Open the Xcontrol .xctl file in a text editor like Notepad.
			** Add the bolded line shown below:
			<Property Name="NI.Lib.Version" Type="Str">1.0.0.0</Property>
			<Property Name="NI.XClass.Flags" Type="Int">0</Property>
			<Property Name="NI.XCtl.OptimizeDataUpdate" Type="Bool">true</Property>
			<Property Name="NI.XItem.DeclaredLeakProof" Type="Bool">false</Property>
			** Save the .xctl file.
			([http://lavag.org/topic/15680-no-update-on-x-control-value-change/page__view__findpost__p__94838 LAVAG source])

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

Michael_Aivaliotis at 07:51, 3 February 2009

2009-02-03T07:51:02Z

← Older revision		Revision as of 07:51, 3 February 2009
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{\| ~~align~~="~~right~~" ~~border~~="0"
	~~\|__TOC__~~		{\| border="0" align="right"
	\|-		\|-
			\| __TOC__
	\|}		\|}
	~~==Introduction==~~
	~~XControls are introduced in LabVIEW 8.0 and enhance the power of front panel objects in great ways.~~

	Essentially an XControl is a front panel object with dedicated code linked in to react on certain user events.		== Introduction ==
			XControls are introduced in LabVIEW 8.0 and enhance the power of front panel objects in great ways.

			Essentially an XControl is a front panel object with dedicated code linked in to react on certain user events.

	An XControl exists of several parts, managed in a .xctl file. The .xctl file is a XML-file like the project-file. Other parts of the XControl are abilities.		An XControl exists of several parts, managed in a .xctl file. The .xctl file is a XML-file like the project-file. Other parts of the XControl are abilities.
	~~==[[XControl:Abilities\|Abilities]]==~~

	==~~[[XControl:Properties\|Properties]]~~==		== Limitations ==
			An XControl functions like a subpanel in the hosting VI. Subpanels (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.

	~~==[[~~XControl~~:Methods\|Methods]]==~~		Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.

	==~~Caveats/Limitations~~==		== Tricks ==
	~~===Limitations===~~		*If you require a variable number of runtime instances of your XControl, Jarrod Slocum of [[National Instruments]] has created an example [http://community.ni.com/examples/linked-object-list-in-labview-8-0-using-xcontrols Linked Object List] based on a Subpanel ''inside'' an XControl.
	An XControl ~~functions like~~ a ~~subpanel in the hosting VI. Subpanels (and therefore XControls)~~ ''~~can not~~'' ~~be placed inside~~ an ~~array. Note that you ''can'' define your~~ XControl ~~data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi~~.

	~~Using LabVIEW native objects~~ (~~.lvclass files~~) ~~inside~~ the ~~state control of an~~ XControl ~~tends to crash LabVIEW for versions less than 8.5.1 when~~ the ~~XControl is used in a different application instance~~.		*If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.

	==~~=Tricks=~~==		== See also ==
	* ~~If you require a variable number of runtime instances of your~~ XControl~~, Jarrod Slocum of~~ [[~~National Instruments~~]] ~~has created an example~~ [~~http~~:~~//community.ni.com/examples/linked-object-list-in-labview-8-0-using-xcontrols Linked Object List~~] ~~based on a Subpanel ''inside'' an XControl.~~		*[[XControl:Properties\|Properties]]
			*[[XControl:Abilities\|Abilities]]
			*[[XControl:Methods\|Methods]]

	* If you want to react to dynamic events (or user events) you need them to register at the XControl Facade '''before''' the event happens.
	[[Category:XControl]]		[[Category:XControl]]

Tcplomp: /* Abilites */ typo

2008-04-02T19:55:02Z

Abilites: typo

← Older revision		Revision as of 19:55, 2 April 2008
Line 10:		Line 10:

	An XControl exists of several parts, managed in a .xctl file. The .xctl file is a XML-file like the project-file. Other parts of the XControl are abilities.		An XControl exists of several parts, managed in a .xctl file. The .xctl file is a XML-file like the project-file. Other parts of the XControl are abilities.
	==[[XControl:Abilities\|~~Abilites~~]]==		==[[XControl:Abilities\|Abilities]]==

	==[[XControl:Properties\|Properties]]==		==[[XControl:Properties\|Properties]]==

Gb119: /* Limitations */ Add note about lvclasses in XControl state crashing LV<8.5.1

2008-03-11T21:07:53Z

Limitations: Add note about lvclasses in XControl state crashing LV<8.5.1

← Older revision		Revision as of 21:07, 11 March 2008
Line 19:		Line 19:
	===Limitations===		===Limitations===
	An XControl functions like a subpanel in the hosting VI. Subpanels (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.		An XControl functions like a subpanel in the hosting VI. Subpanels (and therefore XControls) ''can not'' be placed inside an array. Note that you ''can'' define your XControl data as an array of any LabVIEW data type, and you ''can'' use array controls in the facade vi.

			Using LabVIEW native objects (.lvclass files) inside the state control of an XControl tends to crash LabVIEW for versions less than 8.5.1 when the XControl is used in a different application instance.

	===Tricks===		===Tricks===

← Older revision		Revision as of 04:34, 1 December 2018
Line 38:		Line 38:
	*[[XControl:Abilities\|Abilities]]		*[[XControl:Abilities\|Abilities]]
	*[[XControl:Methods\|Methods]]		*[[XControl:Methods\|Methods]]
			*[[QControl\|QControls]]

	[[Category:XControl]]		[[Category:XControl]]