LabVIEW Wiki - User contributions [en]

LVAddons

2026-03-12T16:25:40Z

Eyesonvis: /* External links */ - replaced link to GitHub document with LabVIEW User Manual topic.

The '''LVAddons''' directory contains drivers and toolkits that are version-independent and therefore do not need to be updated when using different versions of [[LabVIEW]]. It is supported by [[LabVIEW 2022 Q3]] and later.

==Location==
The default location on Windows is "C:\Program Files\NI\LVAddons\". The location can be changed by setting the [[LVAddons.CustomLocation]] configuration key to the desired path. In [[LabVIEW 2024 Q1]] and later, additional locations can be added by setting the [[LVAddons.AdditionalLocations]] configuration key to a semicolon-delimited list of paths. These locations [[wikipedia:superimpose|overlay]] the default or custom location.

==Structure==
The LVAddons directory contains a subdirectory for each add-on, each of which has one or more directories for a version of the add-on. Each version contains a [[lvaddoninfo.json]] file with metadata and directories that contain the add-on files. The folders may reflect any of the [[:Category:folders|folders]] in the LabVIEW installation (e.g., ''vi.lib'').

These directories and files [[wikipedia:superimpose|overlay]] the LabVIEW installation 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]] function with "symbolic path id" set to "<libdir>".

'''Examples'''
{{#tree: minExpandLevel=4 | root=LVAddons |
*dett
**1
***lvaddoninfo.json
***examples
****...
***help
****...
***menus
****...
***resource
****...
*utf32
**1
***lvaddoninfo.json
***examples
****...
***help
****...
***menus
****...
***resource
****...
***templates
****...
***vi.lib
****...
*utf64
**1
***lvaddoninfo.json
***examples
****...
***...
}}

==Adoption==
[[NI]] is actively working on moving drivers and toolkits to the LVAddons directory<ref>[https://www.ni.com/en/support/documentation/supplemental/22/extending-compatibility-between-labview-and-ni-drivers-with-addo.html Extending Compatibility Between LabVIEW and NI Drivers with Add-Ons]</ref>.

==Further use==
In addition to toolkits and drivers, the LVAddons directory can be used to provide version-independent access to custom toolkits, drivers, and libraries. For example, [[PPL]]s or [[wikipedia:dynamic-link library|DLL]]s.

==See also==
*[[GDevCon North America 2024/Modern Development Workflows in LabVIEW]]

==External links==
*[https://www.ni.com/en/support/documentation/supplemental/22/extending-compatibility-between-labview-and-ni-drivers-with-addo.html Extending Compatibility Between LabVIEW and NI Drivers with Add-Ons]
*[https://www.ni.com/docs/en-US/bundle/labview/page/version-independent-add-ons.html Version-Independent LabVIEW Add-ons - NI]

==References==
{{reflist}}

[[Category:Folders]]
[[Category:LVAddons]]

Free label

2025-09-18T22:17:23Z

Eyesonvis: Add details about hyperlinks in free labels

A '''free label''' is a text block on the [[Front Panel]] or [[Block Diagram]]. It is called ''free'' because it does not belong to any specific object as opposed to a regular [[label]].

== Attach to object ==
Free labels can be attached to objects on the Block Diagram. This is indicated by an arrow that originates from the label to the attached object. The link is maintained even when the free label - or the object it is attached to - are moved. Whether or not a free label is attached to an object does not affect the object itself.

== Bookmarks ==
Free labels can be used as [[bookmark]]s for the [[Bookmark Manager]].

== Hyperlinks ==
When free labels contain text that LabVIEW interprets as a hyperlink, the link will be clickable and render in blue. Clicking the link opens it in the default web browser. On the front panel, you can disable automatic conversion of text to links by right-clicking on the label and unchecking ''Enable Hyperlinks''.

LabVIEW identifies hyperlinks by the presence of "://" in the text.

To make a hyperlink where the display text is distinct from the URL, put the display text in angle brackets after the URL. For example: https://labviewwiki.org/<LabVIEW WIKI>

== History ==
{{History|2013|
* Added the ability to attach free labels to objects.
* Added support for [[bookmark]]s.}}
{{History|2015|
* Added support for hyperlinks.}}

[[Category:Programming Elements]]

LabVIEW configuration file/Block Diagram

2025-07-22T16:04:33Z

Eyesonvis: Added LogUnwiredErrors to Block Diagram configuration tokens

This is a list of LabVIEW ini File settings relating to Block Diagram behaviour.

{{TOCnestright}}

{{ labviewconfigurationkey
| keyname = allowDragDropFromFileDlg
| example = allowDragDropFromFileDlg=TRUE
| datatype = b
| description = Enables drag and drop functionality from the file dialog to the block diagram of a vi
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 8.5
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This functionality existed in LV 5.0 -> LV 7.1, was removed in LV 8.x, and added back in as an ini setting in 8.5
}}
{{ labviewconfigurationkey
| keyname = allowOpenFPOfInstanceVIs
| example = allowOpenFPOfInstanceVIs=TRUE
| datatype = b
| description = Changes the behavior of the Convert Instance VI to Standard VI menu option when right-clicking a malleable VI on the block diagram to instead open the instance VI
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2019 onwards
| OS1 = w
| OS2 = m
| OS3 = l
| notes =
}}
{{ labviewconfigurationkey
| keyname = autoWireMax
| example = autoWireMax=24
| datatype = i
| description = Maximum distance between nodes for autowiring to be active
| permitted_values = 1 to 232
| default = 16
| LV1 =6
| LV2 =7
| LV3 =8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This setting is only effective if [[#enableAutoWire|enableAutoWire]] is set to TRUE
}}
{{ labviewconfigurationkey
| keyname = autoWireMin
| example = autoWireMin=8
| datatype = i
| description = Minimum distance between nodes for autowiring to be active
| permitted_values = 1 to 232
| default = 4
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This setting is only effective if [[#enableAutoWire|enableAutoWire]] is set to TRUE
}}
{{ labviewconfigurationkey
| keyname = copyDeleteFPDCOFromFPTerm
| example = copyDeleteFPDCOFromFPTerm=TRUE
| datatype = b
| description = Delete front panel terminals from diagram
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}

{{ labviewconfigurationkey
| keyname = enableAutoWire
| example = enableAutoWire=FALSE
| datatype = b
| description = Enables automatic wire routing. This key is set by the [[Options dialog]] for ''Enable automatic wire routing'' in section [[Block Diagram options#Wiring|Wiring]] under category [[Block Diagram options|Block Diagram]].
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 6
| LV2 = 7
| LV3 = 8
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
}}

{{ labviewconfigurationkey
| keyname = FancyFPTerms
| example = FancyFPTerms=FALSE
| datatype = b
| description = Enables placing front panel terminals as icons. This key is set by the [[Options dialog]] for ''Place front panel terminals as icons'' in section [[Block Diagram options#General|General]] under category [[Block Diagram options|Block Diagram]].
| permitted_values = TRUE or FALSE
| default = (Depends on LV Version)
| LV1 = 7
| LV2 = 8
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
}}

{{ labviewconfigurationkey
| keyname = funkyErrClustWire
| example = funkyErrClustWire=FALSE
| datatype = b
| description = Change Error Cluster wires color from the standard cluster pink to a more distinctive brown/green color
| permitted_values = TRUE or FALSE
| default = LabVIEW 5.1, 6.x, 7.x: FALSE, LabVIEW 8.x: TRUE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = inlineSubVIEnabled
| example = inlineSubVIEnabled=FALSE
| datatype = b
| description = Allows the context menu item "Inline SubVI" on any SubVI which inserts the code directly into the block diagram containing the SubVI.
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = LogUnwiredErrors
| example = LogUnwiredErrors=True
| datatype = b
| description = When enabled, unwired errors are logged to a log file.
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 25.3
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Also supported for built applications.
}}
{{ labviewconfigurationkey
| keyname = maxUndoSteps
| example = maxUndoSteps=50
| datatype = i
| description = Maximum undo steps per VI
| permitted_values = 1 to 99
| default = 8
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = resizeObjectsOnBlockDiagram
| example = resizeObjectsOnBlockDiagram=TRUE
| datatype = b
| description = Enables "Resize Objects" functionality on the block diagram of a vi.
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2015 onward
| OS1 = w
| notes = Mainly useful for resizing objects on the structures palette, comment boxes, and labels.
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example = showBDConstName=TRUE
| datatype = b
| description = Show Constant Label with name of terminal when creating from a terminal
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}

{{ labviewconfigurationkey
| keyname = ShowRedXOnWire
| example = ShowRedXOnWire=TRUE
| datatype = b
| description = Shows a red "X" (and directional arrows) on top of a broken wire.
| permitted_values = TRUE or FALSE
| default = TRUE
| OS1 = w
| OS2 = m
| OS3 = l
}}

{{ labviewconfigurationkey
| keyname = showSubVIName
| example = showSubVIName=TRUE
| datatype = b
| description = Show subVI names when dropped
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showTipStringsOnTerms
| example = showTipStringsOnTerms=FALSE
| datatype = b
| description = Show tip-strips over terminals
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showWireDots
| example = showWireDots=TRUE
| datatype = b
| description = Show dots at wire junctions
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =7
| LV2 =8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showWireGuides
| example = showWireGuides=FALSE
| datatype = b
| description = Show dashed line while wiring
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{labviewconfigurationkey
| keyname = structuresFadeToDiagramBeneath
| example = structuresFadeToDiagramBeneath=FALSE
| datatype = b
| description = Makes the diagram of structures semi-transparent so that you can see objects behind them.
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =6
| LV2 =7
| LV3 =8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = Enabling this setting will slow down the development environment on large Block Diagrams.
}}
{{ labviewconfigurationkey
| keyname = transparentBDLabels
| example = transparentBDLabels=TRUE
| datatype = b
| description = Use transparent name labels
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = UseNumbersForNewVIIcons
| example = UseNumbersForNewVIIcons=FALSE
| datatype = b
| description = Tells LabVIEW whether to automatically include a number (1-9) in the lower-right corner of each new VI's icon.
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 8.6
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes = This key replaces [[#UseNumbersForNewVIIconsInLibs|UseNumbersForNewVIIconsInLibs]] from LabVIEW 8.5.
}}
{{ labviewconfigurationkey
| keyname = UseNumbersForNewVIIconsInLibs
| example = UseNumbersForNewVIIconsInLibs=FALSE
| datatype = b
| description = Tells LabVIEW whether to automatically include a number (1-9) in the lower-right corner of each new VI's icon for VIs created inside libraries (.lvlib, .lvclass, .xctl, .lvsc, etc).
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 8.5
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes = This key was replaced by [[#UseNumbersForNewVIIcons|UseNumbersForNewVIIcons]] in LabVIEW 8.6.
}}
{{ labviewconfigurationkey
| keyname = viCaptionTipStrings
| example = viCaptionTipStrings=FALSE
| datatype = b
| description = Use control captions for subVI tip-strips
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = SourceOnlyEnvironment
| example = SourceOnlyEnvironment=True
| datatype = b
| description = The option "Separate Compiled Code from Source" is turned on by default
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =10
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 =
| OS3 =
| OS4 =
| notes = Currently this causes "uncomfortably" slow load times when opening a large number of VIs which this option enabled. Reference, [https://decibel.ni.com/content/groups/large-labview-application-development/blog/2010/09 NI forums]
}}

[[Category:Configuration File|Block Diagram]]

LVAddons

2025-05-21T15:13:49Z

Eyesonvis: /* External links */ added link to NI's LVAddon documentation on GitHub

The '''LVAddons''' directory contains drivers and toolkits that are version-independent and therefore do not need to be updated when using different versions of [[LabVIEW]]. It is supported by [[LabVIEW 2022 Q3]] and later.

==Location==
The default location on Windows is "C:\Program Files\NI\LVAddons\". The location can be changed by setting the [[LVAddons.CustomLocation]] configuration key to the desired path. In [[LabVIEW 2024 Q1]] and later, additional locations can be added by setting the [[LVAddons.AdditionalLocations]] configuration key to a semicolon-delimited list of paths. These locations [[wikipedia:superimpose|overlay]] the default or custom location.

==Structure==
The LVAddons directory contains a subdirectory for each add-on, each of which has one or more directories for a version of the add-on. Each version contains a [[lvaddoninfo.json]] file with metadata and directories that contain the add-on files. The folders may reflect any of the [[:Category:folders|folders]] in the LabVIEW installation (e.g., ''vi.lib'').

These directories and files [[wikipedia:superimpose|overlay]] the LabVIEW installation 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]] function with "symbolic path id" set to "<libdir>".

'''Examples'''
{{#tree: minExpandLevel=4 | root=LVAddons |
*dett
**1
***lvaddoninfo.json
***examples
****...
***help
****...
***menus
****...
***resource
****...
*utf32
**1
***lvaddoninfo.json
***examples
****...
***help
****...
***menus
****...
***resource
****...
***templates
****...
***vi.lib
****...
*utf64
**1
***lvaddoninfo.json
***examples
****...
***...
}}

==Adoption==
[[NI]] is actively working on moving drivers and toolkits to the LVAddons directory<ref>[https://www.ni.com/en/support/documentation/supplemental/22/extending-compatibility-between-labview-and-ni-drivers-with-addo.html Extending Compatibility Between LabVIEW and NI Drivers with Add-Ons]</ref>.

==Further use==
In addition to toolkits and drivers, the LVAddons directory can be used to provide version-independent access to custom toolkits, drivers, and libraries. For example, [[PPL]]s or [[wikipedia:dynamic-link library|DLL]]s.

==See also==
*[[GDevCon North America 2024/Modern Development Workflows in LabVIEW]]

==External links==
*[https://www.ni.com/en/support/documentation/supplemental/22/extending-compatibility-between-labview-and-ni-drivers-with-addo.html Extending Compatibility Between LabVIEW and NI Drivers with Add-Ons]
*[https://github.com/ni/open-source/blob/main/Documentation/LVAddons-Developer-Documentation.md LVAddons Developer Documentation]

==References==
{{reflist}}

[[Category:Folders]]
[[Category:LVAddons]]

LVCLASS File Extension

2025-01-31T23:01:42Z

Eyesonvis: Added details about changes to the LabVIEW Class file contents in LabVIEW 2025 Q1

The '''LabVIEW Class''' file extension (''*.lvclass'') is used for class libraries in [[LabVIEW object-oriented programming]]. A class library is a special form of [[LabVIEW Project Library|project library]] that defines a new data type in LabVIEW. It contains meta data about the class and its members, a private [[custom control]] that is embedded in the class library (there is no separate file on disk) and links to class methods.

In LabVIEW 2025 Q1, the LabVIEW Class file no longer stores the connector panes of member VIs in binary format. Instead, LabVIEW stores a ''NI.ClassItem.InvokeUsage'' property that is a number:

* 1 = Dynamic method
* 2 = Static property read
* 3 = Static property write
* 4 = Dynamic property read
* 5 = Dynamic property write
* 6 = Data unflatten (loads the class to unflatten a piece of data)
* 7 = Exists (loads the class for the private data control)
* 8 is unused
* 9 = Not a function (used for controls, globals or Polymorphic VIs)

==See also==
*[[Object-oriented programming]]

[[Category:LabVIEW file extensions]]
[[Category:Object-Oriented Programming]]

LVLIB File Extension

2025-01-31T22:52:33Z

Eyesonvis: Documented changes to the LVLIB file contents in LabVIEW 2025 Q1.

The '''LVLIB File Extension''' (''*.lvlib''), or LabVIEW Project Library, are collections of VIs, type definitions, shared variables, palette files, and other files, including other project libraries. When you create and save a new project library, LabVIEW creates a project library file (''.lvlib''), which includes the properties of the project library and the references to files that the project library owns. Do not confused with [[LLB File Extension|LabVIEW Libraries (''*.llb'')]]. See [[LabVIEW Project Library]].

In LabVIEW 2025 Q1, the ''NI_IconEditor'' property's name changed to ''NI.Lib.VIIconTemplate'' to reflect its meaning better. (It stores the template layer icon.)

==See Also==
*[[Packed Project Library]]
*[[LabVIEW Library]]

[[Category:LabVIEW file extensions]]

LVPROJ File Extension

2025-01-31T22:35:37Z

Eyesonvis: Add information about changes to the project file contents in LabVIEW 2025 Q1.

The '''LVPROJ File Extension''' (''*.lvproj''), or LabVIEW Project, consists of a description of [[VI|VIs]], files necessary for those VIs to run properly, and supplemental files such as documentation or related links. [[LabVIEW Project|LabVIEW Projects]] also define build and distribution parameters. Use the [[Project Explorer]] window to manage projects in LabVIEW.

In LabVIEW 2025 Q1, there are two changes to help improve the ability to read and compare project files:

# The project file no longer contains Dependencies. The project dependencies are calculated when LabVIEW loads a project.
# Exported VIs in DLL build specifications have a textual ''ConnectorPane'' property to make changes recognizable. There's still a binary property (''ConnectorPane_Binary''), but it stores the same information.

See [[LabVIEW Project]]

==See Also==
* [[LabVIEW Project]]
* [[Project Explorer]]

[[Category:LabVIEW file extensions]]

Convert Unit function

2024-10-29T15:24:56Z

Eyesonvis: /* External Links */

{{stub}}
{{LabVIEW Palette Object Information|palette=Functions Palette/Programming/Numeric/Conversion{{!}}Conversion palette|type=function|icon=Conversion Palette - Convert Unit.png}}
The '''Convert Unit''' function converts a physical number (a number that has a unit) to a pure number (a number with no units) or a pure number to a physical number. Right-click the function and select Build Unit String from the shortcut menu to build and edit a string of units.
{{TOCright}}
== Usage ==
{{ambox|text=Specific use cases for this function.}}

== History ==
{{ambox|text=History information is needed. What changes have occurred over previous versions?}}
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2018.png|frameless|border|64x64px|LabVIEW 2018|link=LabVIEW 2018]]
|More info to come.
|}
== See Also ==
{{ambox|text=Add links to internal resources that would also help.}}

== External Links ==
- [https://stravaro.com/2021/07/labview-units-part-1/ Let’s Talk About LabVIEW Units, Part 1 - by Brian Powell]
{{ambox|text=Add links to external resources that would also help.}}

[[Category:Conversion Palette]]

Application class/Library.Get Ref By Qualified Name method

2023-08-11T16:02:57Z

Eyesonvis: Fix mistake from LabVIEW docs. This method isn't support on RT.

{{VIServerMethod
| classid = 1
| methodid = 935
| scope=basic
| dataname = Library.Get Ref By Qualified Name
| shortname = Library.Get Ref By Qualified Name
| longname = Library:Get Ref By Qualified Name
| datatypeimage = Library Refnum Indicator.png
| datatype = Library Refnum
| invokenodeimage = Application-Library-Get Ref By Qualified Name.png
| availableinrealtime = No
| availableinruntime = Yes (Read/Write)
| remoteallowed = No
|}}
{{TOCright}}
Retrieves a reference to a LabVIEW project library that is already loaded within the application instance. If the library cannot be found in memory, LabVIEW returns <code>Not A Refnum</code>.
==Parameters==
{| class="wikitable"
|-
! scope="column" style="text-align:Center;" | Data type
! scope="column" style="text-align:Left;" | Name
! scope="column" style="text-align:Left;" | Required
! scope="column" style="text-align:Left;" | Description
|-
! scope="row" style="text-align:Center;" | [[File:Library Refnum Indicator.png|frameless|border|Library Refnum|link=Library Refnum data type]]
| '''Library:Get Ref By Qualified Name'''
| Yes. Return value.
|
|-
! scope="row" style="text-align:Center;" | [[File:String.png|frameless|border|String|link=String data type]]
| '''Qualified Name'''
| Yes
| Qualified name of the project library to which you want LabVIEW to return a reference.
|}

== Uses ==
{{ambox|text=Specific use cases for this method.}}

== History ==
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV8-2013.png|frameless|border|64x64px|LabVIEW 2009|link=LabVIEW 2009]]
| This method was added in [[LabVIEW 2009]].
|}
== See Also ==
{{ambox|text=Add links to internal wiki pages that would also help.}}

== External Links ==
{{ambox|text=Add links to external resources that would also help.}}

[[Category:VI Server Method]]

LabVIEW 2023 Q3

2023-06-05T16:06:54Z

Eyesonvis: Quick Change palette isn't a Quick Drop feature.

{{prevnext|LabVIEW 2023 Q1|LabVIEW Versions|LabVIEW 2024 Q1}}
{{LabVIEW Version
|version=LabVIEW 2023 Q3
|logo=File:LV2023.png
|release=Not yet released.
|change_0=Block diagram zoom
|change_1=Different animation speeds
|change_2=Change label to data type
|change_3=Create controls while wiring
|change_4=Apple silicon support}}

{{ambox
|type=notice
|text=LabVIEW 2023 Q3 is currently in public beta. 
Refer to the [https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/bd-p/labview-2023-beta public beta program] for more information.
There is no guarantee that any of the changes below will be shipped in the final product.
}}

LabVIEW 2023 Q3 Beta was released on April 14th, 2023.<ref name="labview-beta-download"/>

==Added==
* Added [[Block Diagram]] zoom.<ref name="diagram-zoom"/>
* Added the ability to create [[control]]s, [[indicator]]s, or [[constant]]s while wiring.<ref name="create-control-indicator"/>
* Added a [[Quick Change]] menu to change the content of a [[free label]] to a [[Simple data type|simple]] or [[Array data type|array]] data type.<ref name="change-to-object"/>
* Added a [[Quick Change]] palette to wrap the content under a selection rectangle in a [[structure]], or extract it into a [[SubVI]].<ref name="wrap-in-structure"/>
* Added support for [[Find All Instances]] when a VI is running.<ref name="find-all-instances"/>
* Added different animation speeds for [[execution highlighting]]:<ref name="execution-highlighting"/>
** Slow
** Medium (default)
** Fast
** Very Fast
* Added [[corner mark]]s to toolbar buttons that provide additional options:<ref name="corner-markers"/>
** [[Execution highlighting|Highlight Execution]]
** [[Debugging Basics|Step Out]]
* Added support for [[wikipedia:Apple silicon|Apple silicon]].<ref name="apple-silicon"/>

==Changed==
* Changed how the build cache for [[Application]]s, [[Packed Project Library|Packed Project Libraries]] and [[Source Distribution]]s works, so that subsequent builds are much faster.<ref name="build-caching"/>
* Changed the visual feedback when hovering and branching wires.<ref name="wire-highlighting"/>
* Changed the hotkeys to modify the font size to <code>Ctrl</code>+<code><</code> (smaller) and <code>Ctrl</code>+<code>></code> (larger).<ref name="execution-highlighting"/>

==Removed==
Nothing.

==External links==
* [https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/Welcome-to-the-LabVIEW-Public-Beta-Program-in-2023/td-p/4297713 Welcome to the LabVIEW Public Beta Program in 2023!]

==References==
<references>
<ref name="labview-beta-download>[https://www.ni.com/en-us/support/downloads/software-products/download.labview-beta.html#481617 LabVIEW 2023 Q3 Beta]</ref>
<ref name="diagram-zoom">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Diagram-Zoom/td-p/4297781 New Feature: Diagram Zoom]</ref>
<ref name="execution-highlighting">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Multiple-Animation-Speeds-for-Execution-Highlighting/td-p/4297785 New Feature: Multiple Animation Speeds for Execution Highlighting]</ref>
<ref name="change-to-object">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Quick-Change-Label-to-Object/td-p/4298001 New Feature: Quick Change Label to Object]</ref>
<ref name="wrap-in-structure">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Quick-Change-Rectangular-Selection/td-p/4298007 New Feature: Quick Change Rectangular Selection]</ref>
<ref name="create-control-indicator">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Double-click-to-Finish-Wiring-and-Create-Control/td-p/4298009 New Feature: Double-click to Finish Wiring and Create Control/Indicator/Constant]</ref>
<ref name="find-all-instances">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Find-All-Instances-When-Running/td-p/4298073 New Feature: Find All Instances When Running]</ref>
<ref name="wire-highlighting">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-New-Visual-Feedback-When-Selecting-and-Branching/td-p/4298011 New Feature: New Visual Feedback When Selecting and Branching Wires]</ref>
<ref name="build-caching">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Performance-Improvements-to-Building-Applications/td-p/4298080 New Feature: Performance Improvements to Building Applications, Packed Project Libraries and Source Distributions]</ref>
<ref name="apple-silicon">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-LabVIEW-for-macOS-Supports-Apple-Silicon/td-p/4298013 New Feature: LabVIEW for macOS Supports Apple Silicon]</ref>
<ref name="corner-markers">[https://forums.ni.com/t5/LabVIEW-Public-Beta-Program-in/New-Feature-Multiple-Animation-Speeds-for-Execution-Highlighting/m-p/4299630/highlight/true#M56 Re: New Feature: Multiple Animation Speeds for Execution Highlighting]</ref>
</references>

{{stub}} __NOTOC__

[[Category:LabVIEW Versions]]

Event structure

2022-10-17T19:37:51Z

Eyesonvis: Note the behavior of front panel locking with subpanels.

{{TOCright}}
{{LabVIEW Palette Object Information|palette=Functions Palette/Programming/Structures{{!}}Structures palette|palette2=Functions Palette/Programming/Dialog & User Interface/Events{{!}}Events palette|type=structure|icon=Events Palette - Event Structure.png}}
[[File:Event Structure - Components.png|thumb|Components of the Event Structure]]

An '''Event Structure''' is a primitive [[Functions Palette/Programming/Structures|structure]] that can have multiple [[Subdiagram|subdiagrams]] (also known as "Event cases"), one of which is selectively executed at runtime. The structure waits for an event to occur, or until the timeout elapsed. While it waits, it doesn't take up any CPU time. Events can be triggered by user input or programmatically by the software. If an event happens while another event is executing, the new event is put on the [[#The event queue|event queue]].

== Usage ==
=== The event queue ===

Each event structure has an event queue that is managed by LabVIEW. The event queue is processed sequentially by the event structure. It is possible to remove elements from the event queue, using the [[Functions Palette/Programming/Dialog & User Interface/Events/Flush Event Queue|Flush Event Queue]] function. It is not possible to change, destroy or otherwise access the event queue.

=== Event types ===

Events are categorized into dynamic and static events.

==== Dynamic events ====
[[File:Event Structure - Dynamic Events - Dynamic Event Terminals.png|thumb|Dynamic Event Terminals on the Event Structure]]

Dynamic events must be registered at runtime using the [[Register For Events function|Register For Events]] node, connected to the event structure via the ''Dynamic Event Terminals''. The ''Dynamic Event Terminals'' are hidden by default and must be enabled via the right-click menu option '''Show Dynamic Event Terminals'''.

Registered dynamic events are available in the [[#Edit events|configuration dialog]] under [[#Event sources|event sources]] >> [[#Dynamic|Dynamic]].

==== Static events ====

Static events are automatically added to the list of available [[#Event sources|event sources]] and do not have to be registered dynamically. They are generated for the current application, the current VI, panes on the front panel, splitters and controls. Static events are further separated into [[#Notify events|notify events]] and [[#Filter events|filter events]].

===== [[File:Event Structure - Notify Event.png|frameless|border|Notify event]] Notify events =====

Notify events handle a specific event. They are represented in the [[#Edit events|configuration dialog]] by a green arrow: [[File:Event Structure - Notify Event.png|frameless|border|Notify event]]

===== [[File:Event Structure - Filter Event.png|frameless|border|Filter event]] Filter events =====

[[File:Event Structure - Event Filter Node.png|thumb|Event Filter Node on the Event Structure]]

Filter events are executed '''before''' the actual event happens and have an additional '''filter node''' on the subdiagram. The '''filter node''' makes it possible to dynamically ''filter'' (and in some cases even ''alter'') notify events. Filter events are represented in the [[#Edit events|configuration dialog]] by a red arrow: [[File:Event Structure - Filter Event.png|frameless|border|Filter event]]

=== Timeout behavior ===

The timeout terminal on the event structure allows to execute the '''Timeout''' event if no other event has been executed for a certain amount of time. The event structure waits indefinitely if no value is connected to the timeout terminal or if the value is set to a value less than zero. If the timeout is set to a value greater than or equal to zero, the '''Timeout''' event is executed if no other event is executed within the specified period.

=== Edit events ===

[[File:Event Structure - Edit Events Dialog.png|thumb|Configuration dialog for event structures (Edit Events)]]

Events can be configured via the right-click menu options:

{| class="wikitable"
! Option
! Description
|-
| <tt>Edit Events Handled by This Case...</tt>
| Opens the configuration dialog for the current event case.
|-
| <tt>Add Event Case...</tt>
| Adds a new event case to the structure and opens the configuration dialog.
|-
| <tt>Duplicate Event Case...</tt>
| Makes a copy of the currently selected event in a new event case and opens the configuration dialog.
|-
| <tt>Delete This Event Case</tt>
| Deletes the currently selected event case.
|}

The dialog is split into three columns: [[#Event specifiers|Event specifiers]], [[#Event sources|event sources]] and [[#Events|events]].

=== Event specifiers ===

[[File:Event Structure - Edit Events Dialog - Event Specifiers.png|thumb|Event specifiers]]

Lists the event sources and events for the current event case. Each event case can have one or more unique event specifiers. The VI breaks if the same event specifier is used multiple times for the same or different event cases. The '''Add Event''' and '''Remove''' buttons can be used to add or remove events from the list of event specifiers.

=== Event sources ===

[[File:Event Structure - Edit Events Dialog - Event Sources.png|thumb|Event sources]]

Lists the event sources for the current VI. Categories in angle brackets are fixed and always available for all VIs. Grayed-out categories have no event sources.

{| class="wikitable"
! Event source
! Description
|-
| <tt><Application><tt>
| Events for the current application instance (executable)
|-
| <tt><This VI><tt>
| Events for the current VI
|-
| <tt>Dynamic</tt>
| Contains dynamic events registered by the [[#Dynamic events|dynamic events terminal]]
|-
| <tt>Panes</tt>
| Contains entries for [[Subpanel|panels]] on the front panel (by default only "Pane")
|-
| <tt>Splitters</tt>
| Contains entries for [[Splitter|splitters]] on the front panel of the current VI
|-
| <tt>Controls</tt>
| Contains the controls and indicators on the front panel of the current VI. [[Cluster|Clusters]] are nested by their containing controls and indicators.
|}

=== Events ===

[[File:Event Structure - Edit Events Dialog - Events.png|thumb|Events for '''Application''' event source]]
Lists [[#Notify events|notify]] and [[#Filter events|filter]] events for the currently selected event source. The ''filter'' box can be used to search for specific events. The description for each event is available in the [[Help window|help window]] while hovering over an entry in the list.

 

=== Lock panel (defer processing of user actions) until the event case completes ===

{| class="wikitable"
! Status
! Description
|-
| style="text-align: center;" | [[File:Checkbox Checked.png|frameless|border|Checked]]
| The front panel is unresponsive to user input while the event case executes.
|-
| style="text-align: center;" | [[File:Checkbox Unchecked.png|frameless|border|Unchecked]]
| The front panel stays responsive to user input while the event case executes.
|}

This checkbox is ''checked'' by default. When unchecked, any additional events are put on the event queue '''after''' the current event finished executing.

When an event case locks the panel, if the object that generates the event is in a subpanel, then LabVIEW locks the front panel that displays the subpanel.

=== Limit maximum instances of this event in event queue ===

{| class="wikitable"
! Status
! Description
|-
| style="text-align: center;" | [[File:Checkbox Checked.png|frameless|border|Checked]]
| The maximum number of events in the event queue for the current event case is limited to the specified number of '''instances'''.
|-
| style="text-align: center;" | [[File:Checkbox Unchecked.png|frameless|border|Unchecked]]
| The number of events in the event queue is unlimited.
|}

This checkbox is ''unchecked'' by default. When checked, the maximum number of events for the current event case can be defined in the '''Instances''' control below the checkbox.

The limit can only be specified if "[[#Lock panel (defer processing of user actions) until the event case completes|Lock panel (defer processing of user actions) until the event case completes]]" is ''unchecked'' (automatically unchecked by LabVIEW).

== Best practice ==

* Use the [[Producer/Consumer]] [[:Category:Design patterns|design pattern]] to execute time-consuming tasks outside event structures. This will keep the [[Wikipedia:User interface|user interface]] responsive.
* Use [[Functions Palette/Programming/Dialog & User Interface/Cursor/Set Busy|Set Busy]] and [[Functions Palette/Programming/Dialog & User Interface/Cursor/Unset Busy|Unset Busy]] when executing long-running events to give the user a visual feedback.
* Use only one event structure in a [[Functions Palette/Programming/Structures/While Loop|while loop]].
* '''Never''' handle the same event in multiple event structures.
* '''Never''' place an event structure within another event structure.

== FAQ ==

=== Why doesn't the event structure register local variable changes? ===

This is a design choice. Local variables are often used inside an event structure to update values on the front panel. If an event updates the value of the same control that generated the event, it would result in an infinite loop if the event is also generated for local variables. To programmatically generate events for controls use a [[Property node|property node]] for the '''Value (Signaling)''' property.<ref>https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N6xSAE</ref>

== History ==

{| class="wikitable"
! Version
! Change(s)
|-
| [[File:LV8-2013.png|frameless|border|64x64px|LabVIEW 2013|link=LabVIEW 2013]]
| In [[LabVIEW 2013]] unhandled, dynamically registered events do not reset the timeout. Previously, if a dynamic event was registered but there was not an event case in the structure for the event, if the event fired the timeout would still be reset. In [[LabVIEW 2013]] and later if there is not an event case in the structure for the event even if registered then it will not cause the timeout to reset.
|-
| [[File:LV8-2013.png|frameless|border|64x64px|LabVIEW 2011|link=LabVIEW 2011]]
| In [[LabVIEW 2011]] The Value Change is the default event when you define a new event case for a control or indicator.
|-
| [[File:LV7.png|frameless|border|64x64px|LabVIEW 6.1|link=LabVIEW 6i]]
| The Event Structure was added in [[LabVIEW 6i]]. Prior to this version, Event-Driven Programming was not supported.
|}

== See also ==
* [[EventStructure class]]
* [[User events]]
* [[Event Inspector Window]]
* [[Functions Palette/Programming/Dialog & User Interface/Events|Events Palette]]
* [[Producer/Consumer]]

== External links ==

* [http://www.ni.com/tutorial/3331 National Instruments: Event-Driven Programming in LabVIEW]
* [https://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/caveatsrecmndtnsevnts/ National Instruments: Caveats and Recommendations when Using Events in LabVIEW]

== References ==
<references />

[[Category:User interface]]
[[Category:Structures Palette]]
[[Category:Event Structure]]
[[Category:Event-Driven Programming]]
[[Category:Events Palette]]

GLA Summit 2021/gRPC and LabVIEW

2022-02-23T16:46:31Z

Eyesonvis: Add link to video recording

'''gRPC and LabVIEW''' by Christopher Cifra

''NI is investing in supporting idustry standard gRPC as a remote communications transport in a variety of products. This presentation will cover:
* An overview of gRPC
* how NI is using gRPC
* The LabVIEW gRPC support today and future direction
* How members of the community can get involved''

== Presentation Links ==
[https://www.youtube.com/watch?v=0FN9W9tzKaA&t=3s Recording on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]

GLA Summit 2021/Remote and language-agnostic API using gRPC and NI LabVIEW

2022-02-23T16:45:12Z

Eyesonvis: Add link to video recording

'''Remote and language-agnostic API using gRPC and NI LabVIEW''' by Nikita Prorekhin

''gRPC is a modern, open source remote procedure call (RPC) framework that can run anywhere. It enables client and server applications to communicate transparently, and makes it easier to build connected systems. It is a perfect match for microservices or independent LabVIEW modules to enable interprocess communication. In this presentation we will be looking at core gRPC principles and how you can create a gRPC server with LabVIEW using an open-source project from NI (grpc-labview). Along the way we will discuss other use-cases and scenarios where gRPC can be useful.''

== Presentation Links ==
[https://www.youtube.com/watch?v=0DPVrS23RRg Recording on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]

LabVIEW configuration file/Miscellaneous

2012-08-15T18:03:11Z

Eyesonvis:

This is a list of Miscellaneous LabVIEW ini File settings. {{TOCright}}

{{ labviewconfigurationkey
| keyname = BldApp.RemovePolyVIsandTypedefs
| example =BldApp.RemovePolyVIsandTypedefs=FALSE
| datatype =b
| description =Setting this to <code>FALSE</code> stops the LabVIEW Application Builder from aggressively removing polymorphic VIs and typedefs that it thinks are not required
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 7
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.
}}

{{ labviewconfigurationkey
| keyname = coerceFromVariant
| example =coerceFromVariant=TRUE
| datatype =b
| description =Force variants to automatically coerce to any data type that they are connected to
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Tread carefully, as using this function removes coercion notification, and does not use error handling
}}

{{ labviewconfigurationkey
| keyname = cleanupVisa
| example =cleanupVisa=TRUE
| datatype =b
| description =Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = defaultConPane
| example = defaultConPane=4833
| datatype = I32
| description = Sets the default [[Connector pane]] layout for new VIs
| permitted_values =
| default = (4815)
| LV1 = 8.x
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: NI Knowledge Base
( http://digital.ni.com/public.nsf/allkb/279F064F0688C114862570900057678C )
}}

{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}

{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}

{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}

{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = showNoNavDialog
| example =showNoNavDialog=TRUE
| datatype =b
| description =Prevents the "Getting Started Window" dialog from appearing
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =
| OS4 =
| notes = Source: NI Knowledge Base ( http://digital.ni.com/public.nsf/allkb/841B934909D863C886256F62006AC243?OpenDocument )
}}

{{ labviewconfigurationkey
| keyname = ShowTipStrings
| example =ShowTipStrings=FALSE
| datatype =b
| description =Display Tip Strips during execution
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =u
| notes =None
}}

{{ labviewconfigurationkey
| keyname = skipNavigatorDialog
| example =skipNavigatorDialog=TRUE
| datatype =b
| description =Skip the navigation dialog on development environment launch
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = SuperPrivateSpecialStuff
| example =SuperPrivateSpecialStuff=TRUE
| datatype =b
| description =Exposes private properties, method and events in the IDE
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Not supported by NI, this is not a scripting method.
}}

{{ labviewconfigurationkey
| keyname = suppressFileDlgForMissingVIs
| example =suppressFileDlgForMissingVIs=TRUE
| datatype =b
| description =Suppresses the file dialog for when loading a VI that has missing SubVIs
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = useNativeFileDialog
| example =useNativeFileDialog=FALSE
| datatype =b
| description =Use the OS native file dialogs
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = userVIsAppearFirst
| example =userVIsAppearFirst=TRUE
| datatype =b
| description =Makes the user VIs appear first in the tool menu
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 6
| LV2 = 7
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Unfortunately this option no longer works in LabVIEW versions 8+.
}}

{{ labviewconfigurationkey
| keyname = XNodeWizardMode
| example =XNodeWizardMode=TRUE
| datatype =b
| description =Allows contextual menus on [[XNodes]] to facilitate debugging
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = MaxGSWRecentProjects
| example =MaxGSWRecentProjects=10
| datatype =i
| description =Allows more projects to be added to the Getting Started Window
| permitted_values = 1 to 10
| default = 2
| LV1 = 2009
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = operateCursorRunningVIs
| example = operateCursorRunningVIs=TRUE
| datatype =b
| description =Changes the default cursor on running VIs to its behavior prior to LabVIEW 2012
| permitted_values =TRUE or FALSE
| default = FALSE
| LV1 = 2012
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

{{ labviewconfigurationkey
| keyname = useNewProjWiz
| example = useNewProjWiz =FALSE
| datatype =b
| description =Set to FALSE to make the Create Project menu items (in File and Project) open empty projects instead of launching the Create Project dialog.
| permitted_values =TRUE or FALSE
| default = TRUE
| LV1 = 2012
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}

[[Category:Configuration File|Misc]]

LabVIEW configuration file/Miscellaneous

2012-08-15T18:00:37Z

Eyesonvis:

Color

2010-05-05T02:38:09Z

Eyesonvis:

{{TOCright}} 

'''Colors''' are represented in LabVIEW by an unsigned 32-bit integer. The integer is of the hexadecimal form 0x00RRGGBB, where RR, GG, and BB represent the red, green, and blue components of the color, respectively. 

= Special cases =

LabVIEW uses the upper byte (00) for special colors, normally this byte is used for transparency so using these color values in a different program might give odd results. 

== Transparent ==

Transparent has a color value 0x01000000 the last bit of the transparency byte is high, this can be used to create 'holes' controls: 

== System Background ==

This color turns the background into the background of the front-panel/block diagram. It's value is 0x01000037, special details: [[System Label|System_Label]]. 

== System Color ==

LabVIEW supports [http://blog.eyesonvis.com/2010/04/29/system-colors-dont-believe-your-eyes/ six system colors], they match on Windows different color types: 

{| width="600" cellspacing="1" cellpadding="1" border="1" align="left"
|+ System color table
|-
! scope="col" | LabVIEW color name 
! scope="col" | Windows color name 
! scope="col" | LabVIEW color value 
|-
| Panel and Object 
| COLOR_3DFACE 
| 0x01000016 
|-
| Panel and Object text 
| COLOR_BTNTEXT 
| 0x01000006 
|-
| Window 
| COLOR_WINDOW 
| 0x0100000A 
|-
| Window text 
| COLOR_WINDOWTEXT 
| 0x0100000C 
|-
| Highlight 
| COLOR_HIGHLIGHT 
| 0x01000008 
|-
| Highlight text 
| COLOR_HIGHLIGHTTEXT 
| 0x01000009 
|}

 

 

 

 

 

 

 

 

[[Image:ColorDropDownSystem.png]] 

 

There's a VI on ni.com that demonstrates all the LabVIEW system colors, which includes many more than can be selected from the color picker dialog: [http://zone.ni.com/devzone/cda/epd/p/id/4125]

= User colors =

LabVIEW has additional colors that are used for specific elements, like the tank fill color, here's an overview of these colors and their LabVIEW color value, these are not stored with a special value, the following lists the default values for these colors. LabVIEW defines 15 colors per default, but has support for 3 additional colors.

 

{| width="600" cellspacing="1" cellpadding="1" border="1" align="left"
|+ LabVIEW color table
|-
! scope="col" | default LabVIEW color name
! scope="col" | Default LabVIEW color value
|-
| 3D object
| 0x00BCBCBC
|-
| Control background
| 0x00FAFAFA
|-
| Indicator background
| 0x00D2D2D2
|-
| 3D Active object
| 0x00969696
|-
| Text
| 0x00000000
|-
| Led On
| 0x0064FF00
|-
| Led Off
| 0x001E4B00
|-
| Thermometer Fill
| 0x00FF0000
|-
| Slide Fill
| 0x000041DC
|-
| Slide Housing
| 0x006D6D83
|-
| Tank Fill
| 0x000041DC
|-
| Tank Housing
| 0x00A9B3CB
|-
| Classic Object
| 0x00B3B3B3
|-
| Classic Slide Object
| 0x003399FF
|-
| Refnum Wire
| 0x00007F7F
|}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

These color's are stored in the [[LabVIEW configuration file|LabVIEW configuration file]] with the token [[LabVIEW configuration file/Colors#colorUserItem|colorUserItem]] 

 

 

[[Image:ColorDropDownUser.png]] 

== Adjustment ==

To adjust (or add) colors use the LabVIEW options Dialog. In LabVIEW 2009 the colors can be set in the ''Environment'' section. 

A special dialog is available for the 18 supported colors: 

[[Image:ColorAdjustUser.png]] 

 

 

[[Category:Data types]]

Color

2010-05-05T02:33:46Z

Eyesonvis: /* System Color */ Oops, I had two of the colors wrong.

{{TOCright}} 

'''Colors''' are represented in LabVIEW by an unsigned 32-bit integer. The integer is of the hexadecimal form 0x00RRGGBB, where RR, GG, and BB represent the red, green, and blue components of the color, respectively. 

= Special cases =

LabVIEW uses the upper byte (00) for special colors, normally this byte is used for transparency so using these color values in a different program might give odd results. 

== Transparent ==

Transparent has a color value 0x01000000 the last bit of the transparency byte is high, this can be used to create 'holes' controls: 

== System Background ==

This color turns the background into the background of the front-panel/block diagram. It's value is 0x01000037, special details: [[System Label|System_Label]]. 

== System Color ==

LabVIEW supports [http://blog.eyesonvis.com/2010/04/29/system-colors-dont-believe-your-eyes/ six system colors], they match on Windows different color types: 

{| width="600" cellspacing="1" cellpadding="1" border="1" align="left"
|+ System color table
|-
! scope="col" | LabVIEW color name 
! scope="col" | Windows color name 
! scope="col" | LabVIEW color value 
|-
| Panel and Object 
| COLOR_3DFACE 
| 0x01000016 
|-
| Panel and Object text 
| COLOR_BTNTEXT 
| 0x01000006 
|-
| Window 
| COLOR_WINDOW 
| 0x0100000A 
|-
| Window text 
| COLOR_WINDOWTEXT 
| 0x0100000C 
|-
| Highlight 
| COLOR_HIGHLIGHT 
| 0x01000008 
|-
| Highlight text 
| COLOR_HIGHLIGHTTEXT 
| 0x01000009 
|}

 

 

 

 

 

 

 

 

[[Image:ColorDropDownSystem.png]] 

= User colors =

LabVIEW has additional colors that are used for specific elements, like the tank fill color, here's an overview of these colors and their LabVIEW color value, these are not stored with a special value, the following lists the default values for these colors. LabVIEW defines 15 colors per default, but has support for 3 additional colors.

 

{| width="600" cellspacing="1" cellpadding="1" border="1" align="left"
|+ LabVIEW color table
|-
! scope="col" | default LabVIEW color name
! scope="col" | Default LabVIEW color value
|-
| 3D object
| 0x00BCBCBC
|-
| Control background
| 0x00FAFAFA
|-
| Indicator background
| 0x00D2D2D2
|-
| 3D Active object
| 0x00969696
|-
| Text
| 0x00000000
|-
| Led On
| 0x0064FF00
|-
| Led Off
| 0x001E4B00
|-
| Thermometer Fill
| 0x00FF0000
|-
| Slide Fill
| 0x000041DC
|-
| Slide Housing
| 0x006D6D83
|-
| Tank Fill
| 0x000041DC
|-
| Tank Housing
| 0x00A9B3CB
|-
| Classic Object
| 0x00B3B3B3
|-
| Classic Slide Object
| 0x003399FF
|-
| Refnum Wire
| 0x00007F7F
|}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

These color's are stored in the [[LabVIEW configuration file|LabVIEW configuration file]] with the token [[LabVIEW configuration file/Colors#colorUserItem|colorUserItem]] 

 

 

[[Image:ColorDropDownUser.png]] 

== Adjustment ==

To adjust (or add) colors use the LabVIEW options Dialog. In LabVIEW 2009 the colors can be set in the ''Environment'' section. 

A special dialog is available for the 18 supported colors: 

[[Image:ColorAdjustUser.png]] 

 

 

[[Category:Data_types]]

Color

2010-05-01T14:06:44Z

Eyesonvis: /* System Color */

{{TOCright}} 

'''Colors''' are represented in LabVIEW by an unsigned 32-bit integer. The integer is of the hexadecimal form 0x00RRGGBB, where RR, GG, and BB represent the red, green, and blue components of the color, respectively. 

= Special cases =

LabVIEW uses the upper byte (00) for special colors, normally this byte is used for transparency so using these color values in a different program might give odd results. The following colors are available 

== System Color ==

LabVIEW supports [http://blog.eyesonvis.com/2010/04/29/system-colors-dont-believe-your-eyes/ six system colors], they match on Windows different color types: 

{| width="600" cellspacing="1" cellpadding="1" border="1" align="left"
|+ System color table
|-
! scope="col" | LabVIEW color name 
! scope="col" | Windows color name 
! scope="col" | LabVIEW color value 
|-
| Panel and Object 
| COLOR_3DFACE 
| 0x01000016 
|-
| Panel and Object text 
| COLOR_BTNTEXT 
| 0x01000006 
|-
| Window 
| COLOR_WINDOW 
| 0x0100000A 
|-
| Window text 
| COLOR_WINDOWTEXT 
| 0x0100000C 
|-
| Highlight 
| COLOR_MENU 
| 0x01000008 
|-
| Highlight text 
| COLOR_MENUTEXT 
| 0x01000009 
|}

 

 

 

 

 

 

[[Image:ColorDropDownSystem.png]] 

== LabVIEW colors ==

LabVIEW has additional colors that are used for specific elements, like the tank fill color,here's an overview of these colors and their LabVIEW color value, these are not stored with a special value, the following lists the default values for these colors. LabVIEW defines 15 colors per default, but has support for 3 additional colors.

 

{| width="600" cellspacing="1" cellpadding="1" border="1" align="left"
|+ LabVIEW color table
|-
! scope="col" | LabVIEW color name
! scope="col" | Default LabVIEW color value
|-
| 3D object
| 0x00BCBCBC
|-
| Control background
| 0x00FAFAFA
|-
| Indicator background
| 0x00D2D2D2
|-
| 3D Active object
| 0x00969696
|-
| Text
| 0x00000000
|-
| Led On
| 0x0064FF00
|-
| Led Off
| 0x001E4B00
|-
| Thermometer Fill
| 0x00FF0000
|-
| Slide Fill
| 0x000041DC
|-
| Slide Housing
| 0x006D6D83
|-
| Tank Fill
| 0x000041DC
|-
| Tank Housing
| 0x00A9B3CB
|-
| Classic Object
| 0x00B3B3B3
|-
| Classic Slide Object
| 0x003399FF
|-
| Refnum Wire
| 0x00007F7F
|}

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[[Image:ColorDropDownUser.png]] 

=== Adjustment ===

To adjust (or add) colors use the LabVEIW options Dialog. In LabVIEW 2009 the colors can be set in the ''Environment'' section. 

A special dialog is available for the 18 supported colors: 

[[Image:ColorAdjustUser.png]] 

 

 

[[Category:Data_types]]