A '''VI Reference''' [VI-Ref] is a reference to a VI, that is 'somewhere' loaded into the memory of a computer. This VI-
...hine that can be reached via TCP/IP connection. Use the ''Open Application Reference'' node in the Application Control palette. The LabVIEW Help states:
...
2 KB (411 words) - 10:47, 8 October 2007
#REDIRECT [[VI Reference]]
...
26 bytes (3 words) - 12:20, 13 June 2007
#REDIRECT [[Application reference]]
...
35 bytes (3 words) - 07:30, 8 October 2007
-
32 bytes (3 words) - 10:33, 15 April 2007
An '''Applcation Reference''' [AppRef] is a reference to a [[VI Server]], which can operate on the local machine or somewhere on
...lication Reference'' Node on the ''Application Control'' Palette returns a reference to a VI Server Application that runs on the specified computer. If no compu
...
1 KB (166 words) - 07:33, 8 October 2007
The '''Call By Reference''' Node is used to call VIs with a specified connector pane, but without ex
...ust be a strictly typed reference, which can be obtained using the Open VI Reference Node.<br />
...
1 KB (207 words) - 00:08, 13 July 2019
The '''Close Reference function'''...
[[File:Close Reference function.png|thumb|Close Reference function]]
...
593 bytes (74 words) - 07:37, 17 May 2020
'''Reference''' data types, also known as ''"Refnums"'', are temporary pointers to open
...owning VI is still open will no-op, or not operate, and will not close the reference. [[LabVIEW]] automatically closes these refnums when they are no longer ne
...
3 KB (415 words) - 10:00, 30 August 2024
...as the option to return a failure when using [[shift register]]s to pass a reference through a For Loop.
...
530 bytes (79 words) - 07:49, 20 August 2024
| longname = VI Reference
| propertynodeimage = SubVI-VI Reference.png
...
1 KB (127 words) - 19:43, 7 May 2020
| dataname = Create from Reference
| shortname = Create from Reference
...
2 KB (315 words) - 22:22, 7 May 2020
| dataname = Reference
| longname = VI Reference
...
1 KB (203 words) - 13:42, 7 May 2020
| longname = Create:Control Reference
| invokenodeimage = Create-Control Reference.png
...
2 KB (203 words) - 22:23, 7 May 2020
| dataname = Variable Reference
| longname = Variable Reference
...
2 KB (237 words) - 13:42, 7 May 2020
| dataname = Make Strict Reference
| shortname = Make Strict Reference
...
2 KB (206 words) - 22:25, 7 May 2020
| longname = Convert:Call By Reference
| invokenodeimage = CallByRef-Convert-Call By Reference.png
...
1 KB (174 words) - 19:47, 10 June 2020
| longname = Remove Linker Reference
| invokenodeimage = XNode-Remove Linker Reference.png
...
2 KB (273 words) - 22:32, 7 May 2020
| longname = Control Reference Linked To
| propertynodeimage = ControlReferenceConstant-Control Reference Linked To.png
...
1 KB (160 words) - 19:35, 7 May 2020
| longname = Get Active VI Reference
| invokenodeimage = Application-Get Active VI Reference.png
...
2 KB (210 words) - 22:21, 7 May 2020
| longname = VI Reference No Load
| propertynodeimage = ProjectItem-VI Reference No Load.png
...
1 KB (166 words) - 13:42, 7 May 2020
An '''Applcation Reference''' [AppRef] is a reference to a [[VI Server]], which can operate on the local machine or somewhere on
...lication Reference'' Node on the ''Application Control'' Palette returns a reference to a VI Server Application that runs on the specified computer. If no compu
...
1 KB (166 words) - 07:33, 8 October 2007
A '''VI Reference''' [VI-Ref] is a reference to a VI, that is 'somewhere' loaded into the memory of a computer. This VI-
...hine that can be reached via TCP/IP connection. Use the ''Open Application Reference'' node in the Application Control palette. The LabVIEW Help states:
...
2 KB (411 words) - 10:47, 8 October 2007
| longname = Control Reference Linked To
| propertynodeimage = ControlReferenceConstant-Control Reference Linked To.png
...
1 KB (160 words) - 19:35, 7 May 2020
The '''Call By Reference''' Node is used to call VIs with a specified connector pane, but without ex
...ust be a strictly typed reference, which can be obtained using the Open VI Reference Node.<br />
...
1 KB (207 words) - 00:08, 13 July 2019
...in a reference to a VI that stays in memory until you explicitly close the reference.
...
1 KB (183 words) - 13:28, 7 May 2020
|1 = New Data Value Reference function{{!}}New Data Value Reference
|2 = Delete Data Value Reference function{{!}}Delete Data Value Reference
...
2 KB (297 words) - 20:34, 22 June 2020
The '''Close Reference function'''...
[[File:Close Reference function.png|thumb|Close Reference function]]
...
593 bytes (74 words) - 07:37, 17 May 2020
...]] function is being used to cast one [[reference data type]] into another reference data type.
This can sometimes lead to instabilities or crashes with certain reference data types.
...
534 bytes (73 words) - 07:56, 20 August 2024
| dataname = Make Non-Strict Reference
| shortname = Make Non-Strict Reference
...
1 KB (140 words) - 22:25, 7 May 2020
| dataname = Reference
| longname = VI Reference
...
1 KB (203 words) - 13:42, 7 May 2020
...rence to an external data value reference by right-clicking the data value reference and selecting '''External''' from the shortcut menu.
...
1 KB (161 words) - 19:52, 7 May 2020
...as the option to return a failure when using [[shift register]]s to pass a reference through a For Loop.
...
530 bytes (79 words) - 07:49, 20 August 2024
...rence to an external data value reference by right-clicking the data value reference and selecting '''External''' from the shortcut menu.
...
1 KB (163 words) - 19:51, 7 May 2020
* ''Wizard'' (ItemRef) - Reference to the wizard
* ''Item'' (ItemRef) - Reference to the newly created item
...
2 KB (288 words) - 22:26, 21 March 2024
#REDIRECT [[VI Reference]]
...
26 bytes (3 words) - 12:20, 13 June 2007
|1 = Obtain Semaphore Reference function{{!}}Obtain Semaphore Reference
|4 = Release Semaphore Reference function{{!}}Release Semaphore Reference
...
3 KB (374 words) - 19:59, 22 June 2020
| dataname = Make Strict Reference
| shortname = Make Strict Reference
...
2 KB (206 words) - 22:25, 7 May 2020
...ional work to put any outputs into the form expected by the caller. The VI reference must then be returned to the cache.
...reference a would be faster. With that you are in direct control of the VI reference so no cache is involved and the call puts the parameters directly into a pa
...
3 KB (552 words) - 13:50, 11 June 2009
| longname = VI Reference No Load
| propertynodeimage = ProjectItem-VI Reference No Load.png
...
1 KB (166 words) - 13:42, 7 May 2020
| longname = Control Reference Nodes[]
| propertynodeimage = Control Reference Nodes().png
...
1 KB (133 words) - 19:37, 7 May 2020
