LabVIEW Wiki - User contributions [en]

XNODE File Extension

2022-02-12T19:39:56Z

Flarn2006: Fix capitalization and punctuation

This is the file extension for [[XNodes]].

[[Category:Xnode]]
[[Category:LabVIEW file extensions]]

External Node

2022-02-12T19:38:58Z

Flarn2006: Add Xnode category

An '''External Node''' (also formerly known as an XNode, not to be confused with the [[XNode|current meaning]] of that term) is a [[subVI]] whose code determines not only its function, but also its edit-time appearance and behavior. They are similar to modern [[XNodes]] in this respect, but while an XNode is a library containing several Ability VI's, an External Node is a single VI containing a case for each ability. The name of an External Node VI must begin with the characters ";D", not including quotes.

Much like XNodes, External Nodes are not an officially-supported technology for third-party development.

[[Category:Xnode]]

External Nodes

2022-02-12T02:14:00Z

Flarn2006: Update redirect

#REDIRECT [[External Node]]

External Node

2022-02-12T02:13:37Z

Flarn2006: Created page with "An '''External Node''' (also formerly known as an XNode, not to be confused with the current meaning of that term) is a subVI whose code determines not only its..."

Express VI

2022-02-10T03:03:34Z

Flarn2006: Add basic description

{{stub}}

An '''Express VI''' is a special type of [[subVI]] that is configured using a dialog box. LabVIEW ships with many Express VI's, and more can be created from Tools→Advanced→Create or Edit Express VI.

[[Category:Express VI]]

Enumerated type

2022-02-09T03:25:34Z

Flarn2006: /* Shortcomings */

{{TOCnestright}}
Located under the Ring & Enum palette, a LabVIEW enumerated type is used to associate a '''sequential''' numerical value to a programmer defined string

[[Image:Enum_Palette_Location_LV_7.1_and_below.png|frame|center]]

== Potential Uses ==
Enum's can be used with a case selector to provide the programmer an easy way to select a case based on a constant name instead of a number or a string.

[[Image:Enum_connected_to_case_structure.png|frame|center]]

Typedef'd Enum's are often used in [[State Machines]] to provide the programmer an easy way to select new cases without having to worry about spelling mistakes.

== Recommendations ==
Enums are most commonly used to define a fixed list of cases. If the enum will be used as an input or output on the connector pane of a VI, it should be defined as a [[typedef]]. Any changes to the [[typedef]] can be automatically propagated to controls, indicators and constants created from the vi's connector pane.

== Shortcomings ==
LabVIEW enumerated types do not allow for non-sequential values, or what might be known as sparse enums. A [[Ring Constant]] or [[Ring Control]] can be used for this purpose, though the data type will just be a regular integer. 

[[Image:Enum_properties_page.png‎|frame|center]]

==External Links==
* [http://en.wikipedia.org/wiki/Enumerated_type Enumerated type]

[[category:data types]]

Ned options

2022-02-09T03:23:07Z

Flarn2006:

'''Ned, the friendly configuration manager''' is a debug feature of [[LabVIEW]] in form of a window with list of options. The private, internal set of settings available on that list allow changing various aspects of LabVIEW inner mechanisms.

These settings are not saved across LabVIEW sessions, but many of the options are also valid [[LabVIEW configuration file]] keys.

== Enabling Ned Options ==

Like [[Heap Peek]], Ned Options keyboard shortcut is by default disabled in fresh installations of [[LabVIEW]]. To enable it:
* Close LabVIEW
* Put the key "LVdebugKeys=True" in your [[LabVIEW configuration file]]

Then, to trigger the Ned Options window:
* Open your VI
* Press CTRL+SHIFT+D+N. On Mac, use the command key instead of CTRL. This will open the Ned Options window.

== Using Ned Options ==

Clicking once on a option will switch it, cycling through two or more values.

[[Category:Debugging]]
[[Category:LabVIEW internals]]

Heap storage format

2022-02-09T03:20:38Z

Flarn2006: Fix "Resource ID" link

[[Front Panel]] and [[Block Diagram]] of a [[VI|VI file]] are internally called Heaps. Across versions of [[LabVIEW]], several storage formats were used for these heaps.

The format used in currently opened ''VI file'' can be selected in [[Ned options]]. The format used in new ''VI files'' depends on the version of LabVIEW.

'''Note:''' Changing the Heap Storage format in Ned may cause your VI to no longer open! Make sure to experiment on scrap copies of files.

== Binary format 1 ==

Used in first versions of LabVIEW. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHP'' and ''BDHP''.

== Binary format 2 ==

First update of the format, prepared to handle separation of [[Type descriptor|Type Descriptors]] from heap data. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHb'' and ''BDHb''.

== Binary format 3 ==

After this update, all data stored within heap was separated from the main heap tree, dividing heap into two blocks: structure and data. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHc'' and ''BDHc''.

== Verbose Tagged Text ==

A text based format, created to be easily readable by humans. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHT'' and ''BDHT''.

== XML format ==

Since the structure of the heap fits XML format perfectly, would be a sin not to add such option.
Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHX'' and ''BDHX''.

[[Category:LabVIEW internals]]

Resource Container

2022-02-09T03:19:54Z

Flarn2006: /* Known Resources */ Added another VITS example

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], [[RSC File Extension|''*.rsc'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTS
|Front Panel Tags
|Contains data for tags set on front panel objects using the [[Generic class/Tag.Get Tag method|Get Tag]] method.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|BDTS
|Block Diagram Tags
|Contains data for tags set on block diagram objects using the [[Generic class/Tag.Get Tag method|Get Tag]] method.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHT
|Block Diagram Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|FPHT
|Front Panel Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|BDHX
|Block Diagram Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|FPHX
|Front Panel Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file. Consists of a Zlib-compressed data block preceded by four bytes containing the length of the compressed data in big-endian.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private|private methods]] such as [[VI class/Tag.Set Tag|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, [[Express VI]] source VI's have a "_Wizard" tag containing the path to the configuration dialog VI, and the matrix typedefs contain a "NI.LV.All.OperatorInfo1" tag which configures the special "operator overloading" effect they have.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

Resource Container

2022-02-09T03:17:49Z

Flarn2006: added FPTS and BDTS

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], [[RSC File Extension|''*.rsc'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTS
|Front Panel Tags
|Contains data for tags set on front panel objects using the [[Generic class/Tag.Get Tag method|Get Tag]] method.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|BDTS
|Block Diagram Tags
|Contains data for tags set on block diagram objects using the [[Generic class/Tag.Get Tag method|Get Tag]] method.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHT
|Block Diagram Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|FPHT
|Front Panel Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|BDHX
|Block Diagram Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|FPHX
|Front Panel Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file. Consists of a Zlib-compressed data block preceded by four bytes containing the length of the compressed data in big-endian.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private|private methods]] such as [[VI class/Tag.Set Tag|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, the built-in matrix typedefs' "operator overloading" effect is caused by a tag named "NI.LV.All.OperatorInfo1" in the .ctl files.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

VI class/Is Instance property

2022-02-09T02:42:24Z

Flarn2006: Malleable VI's use instances as well

{{VIServerProperty
| classid = 2
| propertyid = 241
| scope=basic
| dataname = Is Instance ?
| shortname = IsInstance
| longname = Is Instance
| datatypeimage = Boolean.png
| datatype = Boolean
| propertynodeimage = VI-Is Instance.png
| availableinrealtime = No
| availableinruntime = No
| availablewithcontrolvis = No
| availablewithglobalvis = Yes
| availablewithpolyvis = No
| availablewithstricttypedefs = No
| loadsbd = No
| loadsfp = No
| mustwait = No
| needsauthentication = No
| permissions = Read/Write
| remoteallowed = Yes
| settablewhenrunning = No
|}}
{{TOCright}}

Returns whether or not the VI is an [[Express VI]] or [[Malleable VI]] instance.

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

== 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 wiki pages that would also help.}}

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

[[Category:VI Server Property]]

ProjectItem

2022-02-02T01:48:55Z

Flarn2006:

A '''Project Item''' is an individual item in a [[LabVIEW Project]], [[LabVIEW Project Library]], [[LabVIEW Class]], or [[XControl]]. A Project Item can be one of many types with an associated type GUID. The [[ProjectItem class]], [[ProjectItem class/Type String property|Type String Property]] can be used to get the ''Type String''. The [[ProjectItem class]], [[ProjectItem class/Type GUID property|Type GUID Property]] can be used to get the ''Type GUID''. In cases where no Type String exists the [[ProjectItem class/Type String property|Type String Property]] returns the Type GUID.

The ''Type String'' is used in the [[ProjectItem class]], [[ProjectItem class/Get All Descendents method|Get All Descendents method]] to get a filtered list of the Descendents by the inputted type. A list of valid ''Type Strings'' with associated ''Type GUIDs'' are listed below. (Add to this list as more are discovered.)

{| class="wikitable"
|-
! Type String
! Type GUID
! Description
|-
| Ability VI
| {DAABD3DA-4F44-4C3D-8BA3-E5D035A4F27A}
| Ability VI within an XControl or XNode
|-
| BeagleBone Black
|
| BeagleBone Black target (available with the [[LabVIEW LINX|LINX Toolkit]])
|-
| Build
| {0C750917-83D7-9871-8908-BB4ED6A8099B}
| Build Specifications node under every target
|-
| Class Private Data
| {64A9BF48-4C55-45DB-8F18-9C796DA0C113}
| Private Data Control inside a LabVIEW Class
|-
| Compact Vision System Target
|
| Real-Time Compact Vision System target
|-
| CompactRIO Ethernet Device
|
| Ethernet RIO target
|-
| CompactRIO Windows
|
| Windows CompactRIO target
|-
| cRIO Chassis
|
| CompactRIO Chassis under a cRIO RT target
|-
| Dependencies
| {0D75D917-83D7-9871-AA09-A0FFD6A8099B}
| Dependencies node under every target
|-
| Directives
|
| Directives items created for VIs by FPGA IP Builder
|-
| DLL
| {20A41099-3F2C-42C3-9544-7ABCC1E6CB0D}
| Shared Library (DLL) node under Build Specifications
|-
| Document
| {D60740D6-F255-4BBC-5675-8858F35B820E}
| Includes:
* Another [[LabVIEW Project]] [[LVLIB File Extension|''(*.lvproj)'']] file when nested inside of a Project
* [[ALIASES File Extension|Aliases ''(*.aliases)'']]
* [[LVLPS File Extension|Local Projects Settings ''(*.lvlps)'']]
* [[LabVIEW Library|LabVIEW Libraries]] [[LLB File Extension|''(*.llb)'']] (Depending on how it was added to the Project)
* [[Run-time Menu]] [[RTM File Extension| ''(*.rtm)'']]
* other Non-LabVIEW files, like images, text files, etc.
|-
| ECATEbusSlave
|
| EtherCAT slave device
|-
| ECATEnetSlave
|
| EtherCAT slave device
|-
| ECATMaster
|
| EtherCAT master device
|-
| EXE
| {9A75366A-79D3-4BFD-9532-E3070185C1E8}
| Application (EXE) node under Build Specifications
|-
| Elemental IO
|
| IO Resource under an FPGA target
|-
| elvisRIO Chassis
|
| Chassis under an ELVIS RIO target
|-
| Embedded Vision System Target
|
| NI Embedded Vision System target
|-
| Folder
| {D60740D6-F254-4BBC-5675-8858F35B820E}
| Includes:
* [[Auto-populating Folder]]s,
* [[Virtual Folder]]s
* [[LabVIEW Library|LabVIEW Libraries]] [[LLB File Extension|''(*.llb)'']] (Depending on how it was added to the Project)
|-
| FPGA Base Clock
|
| Base clock under an FPGA target
|-
| FPGA Component Level IP
|
| RIO DRAM
|-
| FPGA Derived Clock
|
| Derived clock under an FPGA target
|-
| FPGA FIFO
|
| FIFO node under an FPGA target
|-
| FPGA Generic Target
|
| Networked Computer/Device target
|-
| FPGA Memory Block
|
| Memory node under an FPGA target
|-
| FPGA Register
|{730535F4-F2D1-43C7-8D98-0EBD6BAE3470}
| Register item under an FPGA target
|-
| FPGA Target
|
| FPGA target (R-series device, cRIO target, etc.)
|-
| Hyperlink
| {CC472C20-0441-48DC-AF25-3E82ECC9376F}
|
|-
| HTTP WebResources Container
| {CC977D9A-0BF1-470B-B5A7-DF1D00EF9C9B}
| Web Resources folder under a Web Service node
|-
| IO Server
|
| I/O Server node under a target
|-
| IP Builder Target
|
| IP Builder node under an FPGA target
|-
| Installer
| {B912C944-F9D3-49E7-B0A6-073ED50A150B}
| Installer node under Build Specifications
|-
| LVClass (also used for interfaces)
| {EFD740D6-F254-4BBC-5675-8858F35B820E}
| Includes: [[LabVIEW Class]] [[LVCLASS File Extension|''(*.lvclass)'']] and [[Interface (object-oriented programming)|Interfaces]]
|-
| Library
| {ABC740D6-F254-4BBC-5675-8858F35B820E}
| [[LabVIEW Project Library]] [[LVLIB File Extension|''(*.lvlib)'']]
|-
| LibraryData
| {AE832914-DFCB-471F-930C-C57747746FF2}
| Hidden ProjectItem that contains internal information about an LVStatechart library
|-
| Localhost
|
| In some projects with a Real-Time target, the 'My Computer' target will have a type of 'Localhost' instead of 'My Computer'.
|-
| LVLibp
| {CF31838A-5E97-4315-AE50-9EBA613BCBBB}
| [[Packed Project Library]] [[LVLIBP File Extension|''(*.lvlibp)'']]
|-
| LVStatechart
| {FB056C2C-833C-414C-8330-397F164A5211}
| [[LabVIEW StateChart]] [[LVSC File Extension|''(*.lvsc)'']]
|-
| LVStatechartVIItem
| {FB056C2D-833C-414C-8330-397F164A5211}
| Hidden ProjectItem that contains internal information about an LVStatechart library
|-
| Method VI
| {DAABD3DC-4F44-4C3D-8BA3-E5D035A4F27A}
| Method VI in an XControl
|-
| Module Container
|
| Real-Time Scan Resources node under an RT Chassis
|-
| My Computer
| {CEFE1B10-1732-4678-A70A-299293455410}
| My Computer node under the root Project
|-
| NI-DAQmx Task
| {0A806145-1BF3-3A50-0B5E-F969F56C8E2A}
| DAQmx Task
|-
| NI-DAQmx Channel
| {B5F05770-7C71-3A03-C9FB-F73F35629FC1}
| DAQmx Virtual Channel
|-
| NI-DAQmx Scale
| {BC977C97-1833-3D51-4EF6-D82E6838A8F3}
| DAQmx Scale
|-
| Packed Library
| {E4492117-CED3-4F31-9F8D-E2118AE04F12}
| Packed Library node under Build Specifications
|-
| Project
| {D60740D6-F254-4BBC-9975-8858F35B810E}
| Root project item at the top of the [[Project Explorer]] for the [[LabVIEW Project]]
|-
| Property Definition
| {81C68620-8BE3-4643-B04A-4E83AA6363D2}
| Property definition folder under a [[LabVIEW Class]]
|-
| Property Folder
| {D60740D6-F254-4BBC-5675-8858F35B820E}
| Property folder in an [[XControl]]
|-
| Property VI
| {DAABD3DB-4F44-4C3D-8BA3-E5D035A4F27A}
| Property VI in an [[XControl]]
|-
| Raspberry Pi 2 B
| {838AE6B2-6884-4111-A0FB-AF9B59F4094F}
| Raspberry Pi 2 B target (available with the [[LabVIEW LINX|LINX Toolkit]]). Includes Raspberry Pi 3 B+ and 4 B+
|-
| RIO C Series Module
|
| CompactRIO module that appears under the FPGA Target node under an RT CompactRIO target
|-
| RIO Subresource
|
| Resource under a RIO module. For example, an SD Card node.
|-
| RT CDAQ Chassis
|
| Real-Time CompactDAQ Chassis target
|-
| RT CompactRIO
|
| RT CompactRIO target
|-
| RT Desktop
|
| Real-Time Desktop target
|-
| RT elvisRIO
|
| ELVIS RIO target
|-
| RT FlexRIO
|
| Real-Time FlexRIO target
|-
| RT Generic
|
| Generic RT Target
|-
| RT Industrial Controller
|
| Real-Time Industrial Controller target
|-
| RT myRIO
|
| myRIO target
|-
| RT PXI Chassis
|
| RT PXI Target
|-
| RT roboRIO
|
| roboRIO target
|-
| RT Single-Board RIO
|
| RT Single-Board RIO Target
|-
| Robotics Environment Simulator
|
| Simulated robot device
|-
| sbRIO Chassis
|
| Single-Board RIO Chassis that appears under an RT Single-Board RIO target
|-
| Variable
| 9BA597C5-4996-4622-B9BB-444431834D0D}
| Shared Variable node under a library or a target
|-
| Smart Camera Target
|
| Real-Time Industrial Smart Camera Target
|-
| Source Distribution
| {15DA4F9E-0591-4AB1-A339-C3B4D54902D8}
| Source Distribution node under Build Specifications
|-
| Startup VIs Container
| {F0D505FA-F9AD-43D8-8811-2F23BBC4C8A2}
| Startup VIs folder under a Web Service node
|-
| Target Folder
| {AB0740D6-F254-4BBC-5675-8858F35B820E}
|
|-
| TestItem
| {39B74B88-DF2D-4BA8-BEB5-FD65FC0FD56D}
| Test file from the Unit Test Framework [[LVTest File Extension| ''(.lvtest)'']]
|-
| TestVectorItem
| {50E0C210-38A2-420B-AB4E-3BEFFC710090}
| Test vector file from the Unit Test Framework [[LVTest File Extension| ''(.lvvect)'']]
|-
| TouchPanel
|
| Touch Panel target
|-
| VI
| {D60740D6-F254-4BBC-5675-8858F35B810E}
| Includes:
* [[VI]]s [[VI File Extension| ''(.vi)'']]
* [[CTL File Extension|Controls ''(*.ctl)'']]
* [[Polymorphic VI]]s
* [[Malleable VI]]s [[VIM File Extension| ''(.vim)'']]
* [[Global Variable]]s
* [[VI Template]]s [[VIT File Extension| ''(.vit)'']]
|-
| Web Service
| {2386AD17-A358-4EA9-86F1-7808B4D5B5ED}
| Web Service node
|-
| XControl
| {2E4BD3AC-4E04-45C9-B6C5-AD138962C435}
| [[XControl]]
|-
| XNode
| {35CAD751-77A8-4D0F-BF61-85A48475F6A5}
| [[XNode]]
|-
| Zip File
| {51F0E16F-7FA4-4E9F-AE30-C81D9D0444B0}
| Zip File node under Build Specifications
|-
| .NET Interop Assembly
| {0E6E9692-2CDC-4645-B4F6-93F9260BF6FA}
| .NET Interop Assembly node under Build Specifications
|-
| {69A947D5-514E-4E75-818E-69657C0547D8}
| {69A947D5-514E-4E75-818E-69657C0547D8}
| Real-Time Application node under Build Specifications (under an RT Target)
|-
| {117D6E82-86E4-4435-99C8-B638EE47B29E}
| {117D6E82-86E4-4435-99C8-B638EE47B29E}
| Real-Time Application node under Build Specifications (under a Raspberry Pi 2 B Target)
|-
| {9C5E1E31-72F0-41E9-9B17-FFBE4626F549}
| {9C5E1E31-72F0-41E9-9B17-FFBE4626F549}
| IP Build node under Build Specifications (under an IP Builder target)
|-
| {CED73189-3D7D-4B2F-B6C9-EA03FBC59E14}
| {CED73189-3D7D-4B2F-B6C9-EA03FBC59E14}
| Linux RT Package node under Build Specifications
|-
| {E661DAE2-7517-431F-AC41-30807A3BDA38}
| {E661DAE2-7517-431F-AC41-30807A3BDA38}
| Package node under Build Specifications
|-
| {F4C5E96F-7410-48A5-BB87-3559BC9B167F}
| {F4C5E96F-7410-48A5-BB87-3559BC9B167F}
| Compilation node under Build Specifications (under an FPGA target)
|}

[[Category:Project]]

Heap storage format

2022-01-30T05:54:58Z

Flarn2006: /* Verbose Tagged Text */ Added resource ID's for Verbose Tagged Text, and fixed a typo

[[Front Panel]] and [[Block Diagram]] of a [[VI|VI file]] are internally called Heaps. Across versions of [[LabVIEW]], several storage formats were used for these heaps.

The format used in currently opened ''VI file'' can be selected in [[Ned options]]. The format used in new ''VI files'' depends on the version of LabVIEW.

'''Note:''' Changing the Heap Storage format in Ned may cause your VI to no longer open! Make sure to experiment on scrap copies of files.

== Binary format 1 ==

Used in first versions of LabVIEW. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHP'' and ''BDHP''.

== Binary format 2 ==

First update of the format, prepared to handle separation of [[Type descriptor|Type Descriptors]] from heap data. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHb'' and ''BDHb''.

== Binary format 3 ==

After this update, all data stored within heap was separated from the main heap tree, dividing heap into two blocks: structure and data. Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHc'' and ''BDHc''.

== Verbose Tagged Text ==

A text based format, created to be easily readable by humans. Has [[Resource ID]] of ''FPHT'' and ''BDHT''.

== XML format ==

Since the structure of the heap fits XML format perfectly, would be a sin not to add such option.
Has [[Resource_Container#Known_Resources|Resource ID]] of ''FPHX'' and ''BDHX''.

[[Category:LabVIEW internals]]

Heap Peek

2022-01-30T05:53:02Z

Flarn2006: /* Heap View */ Made "exporting a few to XML" a link

Heap Peek is a debug feature available at least since [[LabVIEW 3.0]]. It allows to view internal data structures created for all loaded VI files, including Front Panel Heap and Block Diagram Heap.
The feature is intended for use by LV R&D, though users may in some cases be instructed by LV Support to check something there.

== Enabling Heap Peek ==

The Heap Peek keyboard shortcut is by default disabled in fresh installations of [[LabVIEW]]. To enable it:
* Close LabVIEW
* Put the key "LVdebugKeys=True" in your [[LabVIEW configuration file]]

Then, to trigger the Heap Peek window:
* Open your VI
* Press CTRL+SHIFT+D+H. On Mac, use the command key instead of CTRL. This will open the Heap Peek window.

== Using Heap Peek ==

The window is divided into 5 sections:
* Loaded Container Files are in top-left,
* Heap View is top-right,
* Structure selection for info pane in middle-left,
* Toolbar at the middle,
* Information pane is at base.

The first section, as for usage flow, is top-left one. Start there, by left clicking to select the specific file and specific heap you want to look at.
When the heap is selected, you can display many details on it by clicking rows of either top-right or middle section. These details will show at base, in Information pane.

'''Note:''' Heap Peek only displays information and does not have any ability to change the objects. It does, however, display the locations in memory where the information is stored, which makes it easy to use external memory editing software for this purpose.

== Loaded Container Files list ==

The list is divided into Contexts. In each of these, you can see memory location of the item (within LabVIEW process memory), and entries marked ''BDHP'' or ''FPHP''.
* ''BDHP'' is Block Diagram Heap
* ''FPHP'' is Front Panel Heap

'''Note:''' There are [[VI|VIs]] in LV that are not real VIs (for example, a pseudo VI that is created to represent a Call By Reference to another application instance on another machine), and attempting to do Find to jump to their components can cause problems because those VIs never expect to actually draw themselves.

== Heap View ==

Heap, for LV, is really a [[Front Panel]] or [[Block Diagram]]. Despite the name, they don't really have a heap-like structure. Both FP and BD are stored in form of a tree, strongly inspired by [https://en.wikipedia.org/wiki/XML XML format]. The main difference is - the LV Heap format is binary, not text-based.

In ''Heap View'', Heaps are displayed in a flattened form, not in its full tree-like glory. Part of the entries show properties of the whole pane, and the rest is [[Control|controls]], [[Indicator|indicators]] and other elements added to the pane.

The view for ''FPHP'' reveals that controls and indicators are composed of several [[Control Parts|parts]] - ie. Numeric controls consist of: Label, Frame, Up/Down buttons, Edit field, Radix and Annex. Each [[Control_Parts#List_of_parts|part has partID]], which is used by LV to identify type of that part.

'''Note:''' To learn more about LV Heaps, consider [[Heap storage format|exporting a few to XML]], and looking at them there. The flat list visible in ''Heap View'' will be very helpful when you understand them, but it's not the best way to acquire that understanding.

== Structure selection ==

Here you can select one of the structures within VI files other than ''FPHP''/''BDHP''. These are per-file, not per-heap - so you won't find any difference in them if you select different part of the same file in Loaded Container Files list.

The selectable options are:
* ''VI Fields'' - lists values of many common settings and flags of the VI file
* ''DS Fields'' - lists Data Space properties, including Table of QEs and Table of TMEs
* ''OH Fields''
* ''Stats'' - statistics for objects used within Heaps
* ''Link Info'' - content of all LinkObj lists
* ''Names In Memory''
* ''IL Code Stream'' - Prints Intermediate Language Code used during code compilation process
* ''Code Disassembly'' - Prints assembly generated by the compiler for given VI file
* ''Transform Metrics''
* ''UDClass Info''
* ''Full OMUDClassPtr List''
* ''Available Implementers''

=== DS Fields ===

[[Data Space]] in an important concept in LV internals. In short, ''Data Space'' contains filling for all type mapped [[data type]]s. Be sure to read more on [[Data Space]] to understand it better.

The ''DS Fields'' section contains some general information on [[Data Space]] of the file, and then displays whole mapping of the Data Space (''DSTM''). As of LV2014 it doesn't show values stored in data space, but it shows offsets within said Data Space, and Type Map Entries ('''TME'''s) with information about which data type is stored there, with all its properties. The ''DSTM'' data in this section is cut to only show part of Data Space which is used for different purposes than Heap - the complete Data Space is always larger.

== Toolbar ==

The toolbar consists of several fields.
* Next/prev buttons
* Currently selected item name text
* '''U''' button
* '''F''' button - Click on it to find the object selected in Heap View. LabVIEW will switch to the block diagram or front panel and select related object.
* '''uo''' button - Toggles between sorting the list on the right by UID (the default) or by memory address.

'''Note:''' A previous author said that few developers really know the capacities of heap peek. This is true... it's a debugging tool, and it gets hacked up to debug whatever anyone needs to debug.

[[Category:LabVIEW internals]]
[[Category:Debugging]]

Heap Peek

2022-01-30T05:45:32Z

Flarn2006: /* Toolbar */ Added function of "uo" button, corrected capitalization

Heap Peek is a debug feature available at least since [[LabVIEW 3.0]]. It allows to view internal data structures created for all loaded VI files, including Front Panel Heap and Block Diagram Heap.
The feature is intended for use by LV R&D, though users may in some cases be instructed by LV Support to check something there.

== Enabling Heap Peek ==

The Heap Peek keyboard shortcut is by default disabled in fresh installations of [[LabVIEW]]. To enable it:
* Close LabVIEW
* Put the key "LVdebugKeys=True" in your [[LabVIEW configuration file]]

Then, to trigger the Heap Peek window:
* Open your VI
* Press CTRL+SHIFT+D+H. On Mac, use the command key instead of CTRL. This will open the Heap Peek window.

== Using Heap Peek ==

The window is divided into 5 sections:
* Loaded Container Files are in top-left,
* Heap View is top-right,
* Structure selection for info pane in middle-left,
* Toolbar at the middle,
* Information pane is at base.

The first section, as for usage flow, is top-left one. Start there, by left clicking to select the specific file and specific heap you want to look at.
When the heap is selected, you can display many details on it by clicking rows of either top-right or middle section. These details will show at base, in Information pane.

'''Note:''' Heap Peek only displays information and does not have any ability to change the objects. It does, however, display the locations in memory where the information is stored, which makes it easy to use external memory editing software for this purpose.

== Loaded Container Files list ==

The list is divided into Contexts. In each of these, you can see memory location of the item (within LabVIEW process memory), and entries marked ''BDHP'' or ''FPHP''.
* ''BDHP'' is Block Diagram Heap
* ''FPHP'' is Front Panel Heap

'''Note:''' There are [[VI|VIs]] in LV that are not real VIs (for example, a pseudo VI that is created to represent a Call By Reference to another application instance on another machine), and attempting to do Find to jump to their components can cause problems because those VIs never expect to actually draw themselves.

== Heap View ==

Heap, for LV, is really a [[Front Panel]] or [[Block Diagram]]. Despite the name, they don't really have a heap-like structure. Both FP and BD are stored in form of a tree, strongly inspired by [https://en.wikipedia.org/wiki/XML XML format]. The main difference is - the LV Heap format is binary, not text-based.

In ''Heap View'', Heaps are displayed in a flattened form, not in its full tree-like glory. Part of the entries show properties of the whole pane, and the rest is [[Control|controls]], [[Indicator|indicators]] and other elements added to the pane.

The view for ''FPHP'' reveals that controls and indicators are composed of several [[Control Parts|parts]] - ie. Numeric controls consist of: Label, Frame, Up/Down buttons, Edit field, Radix and Annex. Each [[Control_Parts#List_of_parts|part has partID]], which is used by LV to identify type of that part.

'''Note:''' To learn more about LV Heaps, consider exporting a few to XML, and looking at them there. The flat list visible in ''Heap View'' will be very helpful when you understand them, but it's not the best way to acquire that understanding.

== Structure selection ==

Here you can select one of the structures within VI files other than ''FPHP''/''BDHP''. These are per-file, not per-heap - so you won't find any difference in them if you select different part of the same file in Loaded Container Files list.

The selectable options are:
* ''VI Fields'' - lists values of many common settings and flags of the VI file
* ''DS Fields'' - lists Data Space properties, including Table of QEs and Table of TMEs
* ''OH Fields''
* ''Stats'' - statistics for objects used within Heaps
* ''Link Info'' - content of all LinkObj lists
* ''Names In Memory''
* ''IL Code Stream'' - Prints Intermediate Language Code used during code compilation process
* ''Code Disassembly'' - Prints assembly generated by the compiler for given VI file
* ''Transform Metrics''
* ''UDClass Info''
* ''Full OMUDClassPtr List''
* ''Available Implementers''

=== DS Fields ===

[[Data Space]] in an important concept in LV internals. In short, ''Data Space'' contains filling for all type mapped [[data type]]s. Be sure to read more on [[Data Space]] to understand it better.

The ''DS Fields'' section contains some general information on [[Data Space]] of the file, and then displays whole mapping of the Data Space (''DSTM''). As of LV2014 it doesn't show values stored in data space, but it shows offsets within said Data Space, and Type Map Entries ('''TME'''s) with information about which data type is stored there, with all its properties. The ''DSTM'' data in this section is cut to only show part of Data Space which is used for different purposes than Heap - the complete Data Space is always larger.

== Toolbar ==

The toolbar consists of several fields.
* Next/prev buttons
* Currently selected item name text
* '''U''' button
* '''F''' button - Click on it to find the object selected in Heap View. LabVIEW will switch to the block diagram or front panel and select related object.
* '''uo''' button - Toggles between sorting the list on the right by UID (the default) or by memory address.

'''Note:''' A previous author said that few developers really know the capacities of heap peek. This is true... it's a debugging tool, and it gets hacked up to debug whatever anyone needs to debug.

[[Category:LabVIEW internals]]
[[Category:Debugging]]

Loading vis

2022-01-29T20:08:42Z

Flarn2006: Flarn2006 moved page Loading vis to Loading VIs over redirect: Fixed capitalization

#REDIRECT [[Loading VIs]]

Loading VIs

2022-01-29T20:08:42Z

Flarn2006: Flarn2006 moved page Loading vis to Loading VIs over redirect: Fixed capitalization

{{wikify}}
==Flowchart==

This is a simplified flow chart showing LabVIEW's decision tree when loading a vi into memory from disk. 
Note this diagram applies to LabVIEW 2010 when compiled code is not separated from source code. Other versions may be slightly different. 
[[Image:LoadingLabviewVI.png|center|thumb|500px]]
==Discussion==
'''Aristos Queue''' 

I'm going to try to explain some details of loading a VI. What happens during load depends upon what happened when the VI was last saved, so let's start there. 
 

A good VI is one that has an unbroken run arrow. A broken VI is one that has a red X next to its name in the Error List Window because that VI itself has some problem. A bad VI is one that is listed in the Error List Window because some other VI/library that it depends upon is broken. There's a special case involving typedefs, poly VIs, and global VIs that are in the middle of being edited but are at the moment valid typedefs (i.e., they would not be broken if user did Apply Changes). Such VIs have the pencil icon next to their name in the Error List Window. Those VIs are good, but VIs that use them are bad. 
 
If a VI was good, then we can compile the VI, meaning we can generate the assembly instructions for that VI to run. If a VI is good, when we save, we compile the VI, and we save the compiled code as part of the VI. 
 

If a VI was broken or bad then we can't compile it, so when we save such a VI, we obviously can't save the compiled code. However, a VI might have been good, been compiled, and then become bad without any changes to its own block diagram. In that case, we already have the compiled code for the VI, and so we'll save that with the VI. There's also the special case of a VI that is broken only because it is missing subVIs. We may already have compiled code for such a VI, and so we'll keep that code around if we are asked to save again. (In the case of typedefs, they do have compiled code. They carry the instructions for copying and comparing their data. PolyVIs have no code. I'm not sure about global VIs.) 
 
Ok. That covers save (or, rather, it covers enough of save that we can now talk about load). 
 
When we use the phrase "a VI is in loaded into memory", we really mean, "some portion of the VI's file is in memory in a way that other VIs may link to it and it can be edited and/or executed." If you use the VI Server method "Read Linker Info", that reads the connection information of a VI without loading the VI -- so although we opened the VI file and read some data out of it, we didn't properly make the VI available to the editor and execution system. Same when the palettes load -- they read the icons out of the VIs in the directories, without actually loading the VIs. 
 
There are N parts of a VI, where N is a number I don't remember right now. But for the purposes of this conversation, we can really think of there being just three parts: the front panel (FP), the block diagram (BD) and something I'm going to call "the linker/code block" (LC). That's not a term you'll find anywhere else because I just made it up. The LC is all the stuff that makes a VI be a VI in memory, including: 

*the linker information (the list of other LV files upon which this VI depends)
*the identity of the VI (which library owns this VI)
*the compiled assembly code (unless the VI is broken, in which case there is no compiled assembly code)
*and probably some other stuff not relevant to this conversation.
 
In the development environment, whenever you say File >> Open and load a top-level VI, the LC and FP load into memory. If the VI was last saved as bad or broken or if it turns out to be bad/broken after it finishes loading its dependencies, then the BD also loads into memory. If that VI has subVIs, the LC for all those subVIs load into memory. The FP loads if the subVI is considered necessary (see my earlier post in this thread for things that make that necessary). Both the FP and BD are loaded if those subVIs were saved bad or broken OR if they turn out to be bad/broken once dependencies are loaded. 

 
For all VIs, if an edit is needed during load (say, a subVI conpane changed while the caller was not in memory, or a typedef needs to update, or LV version mutation, or updating the path to a subVI), both FP and BD load. 
 

In the runtime engine, the BD never loads. Obviously, the BD doesn't load if the VI was saved without a block diagram. In a real-time system, neither the FP nor the BD ever load. 

 
After loading the VI (and all its dependencies), if the compiled code is missing and the block diagram is loaded and the VI is not broken/bad, then LV will go ahead and compile the VI and put a docmod on the VI (the little asterisk that means "this VI has unsaved changes"). 
 
The FP and BD will eagerly unload as soon as the reasons for them staying in memory are dealt with. So if you fix a broken VI and then save the changes, FP and BD will unload unless the windows are open or the FP is necessary for the VI. 
 
If you want proof that the diagram loads independently, try this: Save a caller VI and its subVI. Open the caller VI. In the operating system, copy the subVI file on disk to a temp location. Back in LV, open and modify the subVI's diagram. Save the subVI and close the panel and diagram (keep the caller VI open). Now copy the temp file over the subVI file. Now open the block diagram of the subVI again. You'll get one of the more interesting dialogs that LV has to offer, noting that the diagram saved doesn't match the VI in memory and you can either choose not reload the diagram or do load the diagram which will recompile your VI for the new diagram code. If you didn't save the subVI (meaning you choose Defer Decision on the Save Changes dialog), then the diagram is already in memory and I'm pretty sure you won't get that dialog because LV doesn't bother to check disk for stuff it already has loaded. 
'''Daklu''' 
Say you're editing a typedef cluster and all the dependent LC blocks are loaded, but their FP/BD's are not. When the typedef's changes are applied, LV finds all the dependent vis, loads the block diagrams, and makes the necessary edits transparently to the user. (i.e. Without opening windows to the block diagrams.) Since the dependent vis are now dirty their FPs are also loaded into memory, forcing data copies for those FP controls when the app is executed, even though the FP windows aren't open, right? 
'''Aristos Queue''' 
Yes. All that is correct. 
There's another variant -- the FP could be the thing hosting the typedef, and when the typedef changes, LV will load both the FP and the BD into memory in order to update the FP. The reason the BD loads is because the VI has to recompile to deal with the typedef change. 
'''Daklu''' 
Does this behavior change when separating compiled code in LV10? My initial thought is that LV ought to be able to recompile the dependent vi's source code and remove the FP/BD from memory without marking them dirty, and simply wait until the user opens that vi before giving it a dirty dot. But that could lead to confusing behavior when multiple typedef changes are applied sequentially (like what happens when a vi's LC block isn't loaded when changes are applied) so I'm guessing no. 
'''Aristos Queue''' 
I know that it does change. I do not know how dramatic the change is. Your analysis sounds completely plausible, but I haven't really stayed up-to-date on the source-obj splitting. 
'''Daklu''' 
The one open question I still don't have an answer to is why does the FP have to be loaded when the BD loaded? 
'''Aristos Queue''' 
Up until LV 2009, the default values of controls were stored as part of the front panel, so any time the VI wanted to recompile, the panel was actually necessary to generate the code. Nowadays the default values have been moved out of the panel, and we are inching closer to the day when the recompile could happen with just the diagram without the panel, but there are 25 years worth of code that assumes "if I have the diagram then I know the panel is in memory, so I don't have to test for NULL". It's a low priority refactoring that is ooching forward.

==External Links==
Original [http://lavag.org/topic/7015-using-lv-class-vs-passing-cluster/page__view__findpost__p__82679 LAVA] discussion.

[[Category:LabVIEW internals]]

Control Parts

2022-01-29T20:08:04Z

Flarn2006:

Each '''Control''' or '''Indicator''' in LabVIEW consists of '''parts'''. '''Parts''' are the individual elements which make up all [[Control|controls]] within [[Front Panel]] of a [[VI]].

[[Control editor]] allows viewing list of parts in a ''Control'', and modifying their properties. ''Parts'' can also be browsed through [[Heap Peek]], and using XML [[Heap storage format]].

== List of part ID's ==

Every control part contains a "part ID" field which determines its purpose and functionality in the control. For example, a digital numeric control contains two [[BigMultiCosmetic]] parts for the increment and decrement buttons; the part ID is what determines which one is which. The [[Parts Window]] in the control editor displays the part ID as the textual name for the part, though the actual number is only visible in Heap Peek.

{| class="wikitable"
! Part ID
! Long Name
! Description
|-
|1
|Cosmetic
|
|-
|2
|Increment
|
|-
|3
|Decrement
|
|-
|4
|Large Increment
|
|-
|5
|Large Decrement
|
|-
|6
|Pixel Increment
|
|-
|7
|Pixel Decrement
|
|-
|8
|Housing
|
|-
|9
|Frame
|
|-
|10
|Numeric Text
|
|-
|11
|Text
|
|-
|12
|Ring Text
|
|-
|13
|Scrollbar
|
|-
|14
|Ring Picture
|
|-
|15
|Radix
|
|-
|16
|Name Label
|
|-
|17
|Scale
|
|-
|18
|X Scale
|
|-
|19
|Y Scale
|
|-
|20
|Out of Range Box
|
|-
|21
|Boolean Button
|
|-
|22
|Boolean Text
|
|-
|23
|Slider, Needle, or Thumb
|
|-
|24
|Set to Default
|
|-
|25
|Decoration
|
|-
|26
|List Area
|
|-
|27
|Scale Marker
|
|-
|28
|Content Area
|
|-
|29
|DDO Frame
|
|-
|30
|Index Frame
|
|-
|31
|Fill
|
|-
|32
|Graph Legend
|
|-
|33
|Graph Palette
|
|-
|34
|X Fit Button
|
|-
|35
|Y Fit Button
|
|-
|36
|X Fit Lock Button
|
|-
|37
|Y Fit Lock Button
|
|-
|38
|X Scrollbar
|
|-
|39
|Y Scrollbar
|
|-
|40
|Scale Tick
|
|-
|41
|Color Area
|
|-
|42
|Palette Background
|
|-
|43
|Control or Indicator Symbol
|
|-
|44
|Extra Frame Part
|
|-
|45
|Scale Min Tick
|
|-
|46
|Pix Map Palette
|
|-
|47
|Select Button
|
|-
|48
|Text Button
|
|-
|49
|Erase Button
|
|-
|50
|Pen Button
|
|-
|51
|Sucker Button
|
|-
|52
|Bucket Button
|
|-
|53
|Line Button
|
|-
|54
|Rectangle Button
|
|-
|55
|Filled Rectangle Button
|
|-
|56
|Oval Button
|
|-
|57
|Filled Oval Button
|
|-
|58
|Pattern
|
|-
|59
|Foreground Color
|
|-
|60
|Background Color
|
|-
|61
|Pix Map Palette Extra
|
|-
|62
|Zoom Bar
|
|-
|63
|Boolean True Label
|
|-
|64
|Boolean False Label
|
|-
|65
|Unit Label
|
|-
|66
|Annex
|
|-
|67
|Old Graph Cursor
|
|-
|68
|Z Scale
|
|-
|69
|Color Ramp
|
|-
|70
|Output Indicator
|
|-
|71
|X Scale Unit Label
|
|-
|72
|Y Scale Unit Label
|
|-
|73
|Z Scale Unit Label
|
|-
|74
|Graph Move Tool
|
|-
|75
|Graph Zoom Tool
|
|-
|76
|Graph Cursor Tool
|
|-
|77
|Graph X Format
|
|-
|78
|Graph Y Format
|
|-
|79
|Combo Box Button
|
|-
|80
|Diagram Identifier
|
|-
|81
|Menu Title Label
|
|-
|82
|Caption
|
|-
|83
|Refnum Symbol
|
|-
|85
|Formerly Annex2
|
|-
|86
|Boolean Light
|
|-
|87
|Boolean Glyph
|
|-
|88
|Boolean Divot
|
|-
|89
|Boolean Shadow
|
|-
|90
|Tab
|
|-
|91
|Page List Button
|
|-
|92
|Tab Caption
|
|-
|93
|Tab Background
|
|-
|94
|Scale Name
|
|-
|95
|Slide Cap
|
|-
|97
|Contained data type
|
|-
|98
|Position data type
|
|-
|99
|Tab Glyph
|
|-
|100
|Grid
|
|-
|101
|Num Label
|
|-
|102
|Split Bar
|
|-
|103
|Mutli Y-Scrollbar
|
|-
|104
|Graph ViewPort
|
|-
|105
|Grab Handle
|
|-
|106
|Graph Splitter Bar
|
|-
|107
|Graph Legend Area
|
|-
|108
|Graph Legend Scrollbar
|
|-
|109
|Data Binding Status
|
|-
|110
|Ternary Text
|
|-
|111
|Ternary Button
|
|-
|112
|Multi-Segment Pipe Flange
|
|-
|113
|Multi-Segment Pipe Elbow
|
|-
|114
|Multi-Segment Pipe Pipe
|
|-
|115
|Graph Legend Frame
|
|-
|116
|Scene Graph Display
|
|-
|117
|Overflow Status
|
|-
|118
|Radix Shadow
|
|-
|119
|Custom Cosmetic
|
|-
|120
|Typedef Corner
|
|-
|8000
|Non-Colorable Decal
|
|-
|8001
|Digital Display
|
|-
|8002
|Array Index
|
|-
|8003
|Variant Index
|
|-
|8004
|Listbox Display
|
|-
|8005
|Data Display
|
|-
|8006
|Measure Data
|
|-
|8007
|kNotUsed4
|Apparently not a valid part.
|-
|8008
|Tree Legend
|
|-
|8009
|Color Ramp Array
|
|-
|8010
|Type Def's Control
|
|-
|8011
|Cursor Buttons
|
|-
|8012
|High Color
|
|-
|8013
|Low Color
|
|-
|8014
|Graph Cursor
|
|-
|8015
|Graph Scale-legend
|
|-
|8015
|Table
|
|-
|8016
|I/O Name Display
|
|-
|8017
|Tab Control Page Selector
|
|-
|8018
|Browse Button
|
|-
|8019
|Graph Plot Legend
|
|}

[[Category:LabVIEW internals]]
[[Category:Front Panel]]

Resource Container

2022-01-28T22:39:25Z

Flarn2006: Added .rsc extension

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], [[RSC File Extension|''*.rsc'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHT
|Block Diagram Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|FPHT
|Front Panel Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|BDHX
|Block Diagram Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|FPHX
|Front Panel Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file. Consists of a Zlib-compressed data block preceded by four bytes containing the length of the compressed data in big-endian.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private|private methods]] such as [[VI class/Tag.Set Tag|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, the built-in matrix typedefs' "operator overloading" effect is caused by a tag named "NI.LV.All.OperatorInfo1" in the .ctl files.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

Resource Container

2022-01-28T22:38:11Z

Flarn2006: Added VCTP compression details

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHT
|Block Diagram Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|FPHT
|Front Panel Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|BDHX
|Block Diagram Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|FPHX
|Front Panel Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file. Consists of a Zlib-compressed data block preceded by four bytes containing the length of the compressed data in big-endian.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private|private methods]] such as [[VI class/Tag.Set Tag|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, the built-in matrix typedefs' "operator overloading" effect is caused by a tag named "NI.LV.All.OperatorInfo1" in the .ctl files.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

Resource Container

2022-01-28T01:33:03Z

Flarn2006: /* Known Resources */ Added more VITS details

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHT
|Block Diagram Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|FPHT
|Front Panel Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|BDHX
|Block Diagram Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|FPHX
|Front Panel Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|Contains a VI's persistent tags. Tags are additional data which is attached to a VI and manipulated using [[VI Server#Private|private methods]] such as [[VI class/Tag.Set Tag|VI class/Tag.Set Tag]] on the VI object. Certain tags can affect LabVIEW's functionality; for example, the built-in matrix typedefs' "operator overloading" effect is caused by a tag named "NI.LV.All.OperatorInfo1" in the .ctl files.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

Heap Peek

2022-01-27T21:01:44Z

Flarn2006: /* Using Heap Peek */

Heap Peek is a debug feature available at least since [[LabVIEW 3.0]]. It allows to view internal data structures created for all loaded VI files, including Front Panel Heap and Block Diagram Heap.
The feature is intended for use by LV R&D, though users may in some cases be instructed by LV Support to check something there.

== Enabling Heap Peek ==

The Heap Peek keyboard shortcut is by default disabled in fresh installations of [[LabVIEW]]. To enable it:
* Close LabVIEW
* Put the key "LVdebugKeys=True" in your [[LabVIEW configuration file]]

Then, to trigger the Heap Peek window:
* Open your VI
* Press CTRL+SHIFT+D+H. On Mac, use the command key instead of CTRL. This will open the Heap Peek window.

== Using Heap Peek ==

The window is divided into 5 sections:
* Loaded Container Files are in top-left,
* Heap View is top-right,
* Structure selection for info pane in middle-left,
* Toolbar at the middle,
* Information pane is at base.

The first section, as for usage flow, is top-left one. Start there, by left clicking to select the specific file and specific heap you want to look at.
When the heap is selected, you can display many details on it by clicking rows of either top-right or middle section. These details will show at base, in Information pane.

'''Note:''' Heap Peek only displays information and does not have any ability to change the objects. It does, however, display the locations in memory where the information is stored, which makes it easy to use external memory editing software for this purpose.

== Loaded Container Files list ==

The list is divided into Contexts. In each of these, you can see memory location of the item (within LabVIEW process memory), and entries marked ''BDHP'' or ''FPHP''.
* ''BDHP'' is Block Diagram Heap
* ''FPHP'' is Front Panel Heap

'''Note:''' There are [[VI|VIs]] in LV that are not real VIs (for example, a pseudo VI that is created to represent a Call By Reference to another application instance on another machine), and attempting to do Find to jump to their components can cause problems because those VIs never expect to actually draw themselves.

== Heap View ==

Heap, for LV, is really a [[Front Panel]] or [[Block Diagram]]. Despite the name, they don't really have a heap-like structure. Both FP and BD are stored in form of a tree, strongly inspired by [https://en.wikipedia.org/wiki/XML XML format]. The main difference is - the LV Heap format is binary, not text-based.

In ''Heap View'', Heaps are displayed in a flattened form, not in its full tree-like glory. Part of the entries show properties of the whole pane, and the rest is [[Control|controls]], [[Indicator|indicators]] and other elements added to the pane.

The view for ''FPHP'' reveals that controls and indicators are composed of several [[Control Parts|parts]] - ie. Numeric controls consist of: Label, Frame, Up/Down buttons, Edit field, Radix and Annex. Each [[Control_Parts#List_of_parts|part has partID]], which is used by LV to identify type of that part.

'''Note:''' To learn more about LV Heaps, consider exporting a few to XML, and looking at them there. The flat list visible in ''Heap View'' will be very helpful when you understand them, but it's not the best way to acquire that understanding.

== Structure selection ==

Here you can select one of the structures within VI files other than ''FPHP''/''BDHP''. These are per-file, not per-heap - so you won't find any difference in them if you select different part of the same file in Loaded Container Files list.

The selectable options are:
* ''VI Fields'' - lists values of many common settings and flags of the VI file
* ''DS Fields'' - lists Data Space properties, including Table of QEs and Table of TMEs
* ''OH Fields''
* ''Stats'' - statistics for objects used within Heaps
* ''Link Info'' - content of all LinkObj lists
* ''Names In Memory''
* ''IL Code Stream'' - Prints Intermediate Language Code used during code compilation process
* ''Code Disassembly'' - Prints assembly generated by the compiler for given VI file
* ''Transform Metrics''
* ''UDClass Info''
* ''Full OMUDClassPtr List''
* ''Available Implementers''

=== DS Fields ===

[[Data Space]] in an important concept in LV internals. In short, ''Data Space'' contains filling for all type mapped [[data type]]s. Be sure to read more on [[Data Space]] to understand it better.

The ''DS Fields'' section contains some general information on [[Data Space]] of the file, and then displays whole mapping of the Data Space (''DSTM''). As of LV2014 it doesn't show values stored in data space, but it shows offsets within said Data Space, and Type Map Entries ('''TME'''s) with information about which data type is stored there, with all its properties. The ''DSTM'' data in this section is cut to only show part of Data Space which is used for different purposes than Heap - the complete Data Space is always larger.

== Toolbar ==

The toolbar consists of several fields.
* Next/prev buttons
* Currently selected item name text
* U button
* F button - Click on it to find the object selected in Heap View. LabVIEW will switch to the block diagram or front panel and select related object.
* UO button

'''Note:''' A previous author said that few developers really know the capacities of heap peek. This is true... it's a debugging tool, and it gets hacked up to debug whatever anyone needs to debug.

[[Category:LabVIEW internals]]
[[Category:Debugging]]

VI Server

2022-01-22T19:06:25Z

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

[[File:VI Server.png|thumb|452x452px|VI Server - Open Reference, Property Node, Close Reference]]
'''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, (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.
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 ==

=== Basic Development Environment ===
[[File:VI Server Basic.png|thumb|283x283px|Basic VI Server Calls]]
The Basic Development Environment holds all of the basic functions to modify properties and methods for:
* Controls and Indicators
* Panes and Panels
* VIs
* [[ProjectItem]] (Projects, Libraries, and Classes)
* 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:
* Deprecated
* Private
* Scripting
* Basic
Meaning if one property in a Property Node is Deprecated and all others are one of the other types, the property will appear red for the deprecated property.

=== VI Scripting ===
[[File:VI Server Scripting.png|thumb|294x294px|Scripting VI Server Calls]]
[[VI Scripting]] adds functionality to modify properties and methods for:
* Block Diagram
** Primitives
** Structures
** Terminals

* Connector Pane
When scripting is enabled the Class Specifier Constant, Property Nodes, and Invoke Nodes turn light cyan when containing scripting Classes, Properties and Methods, respectively. If scripting functions are being used but scripting is then disabled, they will continue to work but will appear the standard yellow and will no longer be discoverable.

=== Private ===
[[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.'''

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.

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 ===
[[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. 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 ==
[https://forums.ni.com/t5/LabVIEW-APIs-Discussions/Exploring-the-Depths-of-the-VI-Server/td-p/3844848 Exploring the Depths of the VI Server] - by Quentin Alldredge, Q Software Innovations

''This presentation goes into the depths of the VI Server including Basic LabVIEW, VI Scripting, and even the Private stuff, showing many of the Properties, Methods, and Events I have found useful in the creation of LabVIEW IDE add-ons.''

== Tools ==
[https://gitlab.com/QSI_Shared_Code/VIServerToolkit.git VI Server Toolkit] - shared code library for discovering the Classes, Properties, Methods, and Events in the VI Server.

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

Ned

2022-01-22T19:00:49Z

Flarn2006: Redirected page to Ned options

#REDIRECT [[Ned options]]

Project Provider Framework

2022-01-18T20:05:08Z

Flarn2006: Update to reflect public release of PPF

The Project Provider Framework is an unsupported API used to extend LabVIEW in various ways, mostly relating to the project interface. While NI does not provide official support for Project Providers, nor guarantee their stability in future versions, they have provided some documentation as well as a community forum for the framework; this was originally only available to NI-approved developers, but has since been opened to the general public.

A Project Provider is defined by an INI file located in the <code>resource/Framework/Providers/GProviders</code> directory in the LabVIEW installation directory. This file contains paths to "interface VI's", which determine the locations of other VI's that implement the plugin's functionality.

==Signature==
For LabVIEW to load a project provider, its INI file must contain a valid "signature" consisting of an enciphered MD5 hash of certain other values in the INI file, generated using a signing tool provided by NI. This is an artifact from before the framework was officially made public, though the method of generating the signature had been reverse engineered and was publicly known prior to that point.

===Algorithm===
What follows is an explanation of how the "signature" is determined. If you are using the official signing tool (or an unofficial one) you do not need to know this, but it might be useful for tool developers or anyone who is curious.

First, take the ''values'' (not the keys) in the INI file in order, and concatenate them. Only include the values for keys in this list (rule of thumb: string values, not Boolean or numeric values, and don't include the Signature key of course):

* "InterfaceVersion"
* "LicenseRestrictions"
* "LicenseVersion"
* "LicenseName"
* "Alias"
* "SupportedType"
* "SupportedInterface"
* "CreateNewWizardHost"
* "BuildInterfaceVI"
* "DeployInterfaceVI"
* "SourceControlInterfaceVI"
* "CreateNewWizardInterfaceVI"
* "GlobalItemInterfaceVI"
* "ProviderInterfaceVI"
* "ItemInterfaceVI"

Do not include spaces or any other types of delimiters between values in the concatenated string. Take the MD5 hash of this string, and apply the following substitution cipher to each of the digits:

Change: 0123456789ABCDEF
To: T3C5K7W9SBNRJLX2

Finally, for each pair of two consecutive digits, switch them. For example, CRTTR3X7 would become RCTT3R7X. You now have your signature!

==See also==
* [https://forums.ni.com/t5/LabVIEW-Project-Providers/bd-p/bymqyodmkc NI Project Provider discussion forum]
* [https://forums.ni.com/t5/LabVIEW-Project-Providers/Project-Providers-Documentation/td-p/3492573 Official documentation thread]
* [https://forums.ni.com/t5/LabVIEW-Project-Providers/Project-Provider-INI-File-Signer-Tool/m-p/3534658 Project Provider INI File Signer Tool]
* [http://lavag.org/topic/18545-i-have-taken-the-first-step-towards-unofficially-opening-up-the-project-provider-framework/ Unofficial LAVA post about reverse-engineered signature algorithm]

[[Category:Frameworks]]
[[Category:IDE Add-ons]]

LabVIEW configuration file/Miscellaneous

2021-08-23T04:26:35Z

Flarn2006: Clarify bit about Xnode license

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

{{ labviewconfigurationkey
| keyname = ActiveXMoreContainerOptions
| example = ActiveXMoreContainerOptions=FALSE
| datatype = b
| description = Adds "Persist State To Edit Mode" and "Destroy And Recreate When Run" to the Advanced submenu of an ActiveX container<ref name="lava-18469">[https://lavag.org/topic/18469-i-found-some-more-hidden-ini-keys/ I found some more hidden INI keys (LAVA)]</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
}}

{{ 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 = EnableStrictTypedefConstantConfiguration
| example = EnableStrictTypedefConstantConfiguration=FALSE
| datatype = b
| description = Adds a new context menu item to constants based on strict typedefs called Act as Strict Typedef Constant. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = GenericsAreGo
| example = GenericsAreGo=TRUE
| datatype = b
| description = Adds a context-menu item to controls and indicators labeled "Generic". This activates an abandoned feature in LabVIEW enabling the creation of "[[Generic VIs]]". If a control marked "generic" is connected to a VI's connector pane, it will automatically change to whatever type is wired to it; an indicator marked "generic" shows similar behavior with its block diagram terminal. If this just sounds like [[Malleable VIs]] with extra steps, that's because this is an unfinished prototype of what eventually became that. '''Using them is a BAD IDEA, unless you just want to experiment with it as a curiosity. NI staff have warned against using this in any kind of production code, as it is very buggy, abandoned for a reason, and can corrupt VI's. Use Malleable VI's instead; they do the same thing much better without using buggy unfinished features.'''
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2014
| LV2 =
| 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 = ShowHiddenLibraryItems
| example = ShowHiddenLibraryItems=FALSE
| datatype = b
| description = Shows hidden library items (for example when editing a statechart library). <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = showRunAtAnyLoopMenuItem
| example = showRunAtAnyLoopMenuItem=FALSE
| datatype = b
| description = Adds a new menu item to Property and Invoke nodes labeled "Run At Any Loop". When selected, the node turns brown as if a private property or method was selected, even if none are. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SimShowCompanionDiag
| example = SimShowCompanionDiag=FALSE
| datatype = b
| description = Adds a context menu option to the Simulation structure called "Show Companion Diagram", which toggles showing what looks like a "behind-the-scenes" block diagram for the simulation. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SuperSecretPrivateSpecialStuff
| example =SuperSecretPrivateSpecialStuff=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 = useUnicode
| example = useUnicode=FALSE
| datatype = b
| description = Enables Unicode characters in LabVIEW. <ref name="thelvlab">[https://thelvlab.wixsite.com/thelabviewlab/single-post/2017/12/21/All-the-LabVIEWini-Treasures-You-Were-Looking-For All the LabVIEW.ini Treasures You Were Looking For] (The LabVIEW Lab)</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
| OS2 = m
| OS3 = l
| notes = Unicode is not fully supported in LabVIEW. Use with caution!
}}

{{ 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 = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Displays window titles instead of VI names in functions palettes. This key is set by the [[Controls/Functions Palettes options#Formatting|Use window titles in functions palette]] option in the [[Controls/Functions Palettes options|Controls/Functions Palettes]] category of the [[Options dialog]].
| permitted_values = TRUE or FALSE
| default = TRUE
| OS1 = w
| OS2 = m
| OS3 = l
}}

{{ labviewconfigurationkey
| keyname = XNodeDevelopment_LabVIEWInternalTag
| example =XNodeDevelopment_LabVIEWInternalTag=True
| datatype =b
| description =Enables [[XNode|XNodes]] to be edited and created within LabVIEW.
| permitted_values =TRUE or FALSE
| default =FALSE
| OS1 =m
| OS2 =l
| notes =This configuration key does not work on Windows, as on that version it is enabled via an "XNodeDevelopment" license which is only available to NI employees; thus, there is no way to access this functionality on the Windows version without violating the license agreement. When enabled, regardless of OS, "XNode" will appear in the File->New dialog.
}}

{{ 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
}}

{{ labviewconfigurationkey
| keyname = QuickBold
| example = QuickBold=TRUE
| datatype = b
| description = When editing text (either on the block diagram or the front panel) Ctrl-B allows you to toggle '''bold''' on or off. (When not editing text, Ctrl-B still performs it's normal function: remove broken wires.)
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2013
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

{{ labviewconfigurationkey
| keyname = ShowConsoleForPythonNode
| example = ShowConsoleForPythonNode=TRUE
| datatype = b
| description = Shows the output from Python when a Python Node executes.<ref name="ni-ShowConsoleForPythonNode"/>
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2018 and later
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

== References ==
<references>
<ref name="ni-ShowConsoleForPythonNode">[https://forums.ni.com/t5/LabVIEW-2021-Public-Beta/New-Feature-Improved-Python-Support/m-p/4147033/highlight/true#M87 Improved Python Support (LabVIEW 2021 Public Beta)] by Christina Rogers</ref>
</references>

[[Category:Configuration File|Misc]]

LabVIEW configuration file/Miscellaneous

2021-08-23T04:21:24Z

Flarn2006: Update GenericsAreGo description that obviously predates the existence of Malleable VI's.

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

{{ labviewconfigurationkey
| keyname = ActiveXMoreContainerOptions
| example = ActiveXMoreContainerOptions=FALSE
| datatype = b
| description = Adds "Persist State To Edit Mode" and "Destroy And Recreate When Run" to the Advanced submenu of an ActiveX container<ref name="lava-18469">[https://lavag.org/topic/18469-i-found-some-more-hidden-ini-keys/ I found some more hidden INI keys (LAVA)]</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
}}

{{ 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 = EnableStrictTypedefConstantConfiguration
| example = EnableStrictTypedefConstantConfiguration=FALSE
| datatype = b
| description = Adds a new context menu item to constants based on strict typedefs called Act as Strict Typedef Constant. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = GenericsAreGo
| example = GenericsAreGo=TRUE
| datatype = b
| description = Adds a context-menu item to controls and indicators labeled "Generic". This activates an abandoned feature in LabVIEW enabling the creation of "[[Generic VIs]]". If a control marked "generic" is connected to a VI's connector pane, it will automatically change to whatever type is wired to it; an indicator marked "generic" shows similar behavior with its block diagram terminal. If this just sounds like [[Malleable VIs]] with extra steps, that's because this is an unfinished prototype of what eventually became that. '''Using them is a BAD IDEA, unless you just want to experiment with it as a curiosity. NI staff have warned against using this in any kind of production code, as it is very buggy, abandoned for a reason, and can corrupt VI's. Use Malleable VI's instead; they do the same thing much better without using buggy unfinished features.'''
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2014
| LV2 =
| 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 = ShowHiddenLibraryItems
| example = ShowHiddenLibraryItems=FALSE
| datatype = b
| description = Shows hidden library items (for example when editing a statechart library). <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = showRunAtAnyLoopMenuItem
| example = showRunAtAnyLoopMenuItem=FALSE
| datatype = b
| description = Adds a new menu item to Property and Invoke nodes labeled "Run At Any Loop". When selected, the node turns brown as if a private property or method was selected, even if none are. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SimShowCompanionDiag
| example = SimShowCompanionDiag=FALSE
| datatype = b
| description = Adds a context menu option to the Simulation structure called "Show Companion Diagram", which toggles showing what looks like a "behind-the-scenes" block diagram for the simulation. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SuperSecretPrivateSpecialStuff
| example =SuperSecretPrivateSpecialStuff=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 = useUnicode
| example = useUnicode=FALSE
| datatype = b
| description = Enables Unicode characters in LabVIEW. <ref name="thelvlab">[https://thelvlab.wixsite.com/thelabviewlab/single-post/2017/12/21/All-the-LabVIEWini-Treasures-You-Were-Looking-For All the LabVIEW.ini Treasures You Were Looking For] (The LabVIEW Lab)</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
| OS2 = m
| OS3 = l
| notes = Unicode is not fully supported in LabVIEW. Use with caution!
}}

{{ 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 = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Displays window titles instead of VI names in functions palettes. This key is set by the [[Controls/Functions Palettes options#Formatting|Use window titles in functions palette]] option in the [[Controls/Functions Palettes options|Controls/Functions Palettes]] category of the [[Options dialog]].
| permitted_values = TRUE or FALSE
| default = TRUE
| OS1 = w
| OS2 = m
| OS3 = l
}}

{{ labviewconfigurationkey
| keyname = XNodeDevelopment_LabVIEWInternalTag
| example =XNodeDevelopment_LabVIEWInternalTag=True
| datatype =b
| description =Enables [[XNode|XNodes]] to be edited and created within LabVIEW.
| permitted_values =TRUE or FALSE
| default =FALSE
| OS1 =m
| OS2 =l
| notes =This configuration key does not work on Windows, as it must instead be enabled via the license manager in that version. When enabled, "XNode" will appear in the File->New dialog.
}}

{{ 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
}}

{{ labviewconfigurationkey
| keyname = QuickBold
| example = QuickBold=TRUE
| datatype = b
| description = When editing text (either on the block diagram or the front panel) Ctrl-B allows you to toggle '''bold''' on or off. (When not editing text, Ctrl-B still performs it's normal function: remove broken wires.)
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2013
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

{{ labviewconfigurationkey
| keyname = ShowConsoleForPythonNode
| example = ShowConsoleForPythonNode=TRUE
| datatype = b
| description = Shows the output from Python when a Python Node executes.<ref name="ni-ShowConsoleForPythonNode"/>
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2018 and later
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

== References ==
<references>
<ref name="ni-ShowConsoleForPythonNode">[https://forums.ni.com/t5/LabVIEW-2021-Public-Beta/New-Feature-Improved-Python-Support/m-p/4147033/highlight/true#M87 Improved Python Support (LabVIEW 2021 Public Beta)] by Christina Rogers</ref>
</references>

[[Category:Configuration File|Misc]]

LabVIEW configuration file/Miscellaneous

2020-09-27T15:34:20Z

Flarn2006: XNodeDevelopment_LabVIEWInternalTag

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

{{ labviewconfigurationkey
| keyname = ActiveXMoreContainerOptions
| example = ActiveXMoreContainerOptions=FALSE
| datatype = b
| description = Adds "Persist State To Edit Mode" and "Destroy And Recreate When Run" to the Advanced submenu of an ActiveX container<ref name="lava-18469">[https://lavag.org/topic/18469-i-found-some-more-hidden-ini-keys/ I found some more hidden INI keys (LAVA)]</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
}}

{{ 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 = EnableStrictTypedefConstantConfiguration
| example = EnableStrictTypedefConstantConfiguration=FALSE
| datatype = b
| description = Adds a new context menu item to constants based on strict typedefs called Act as Strict Typedef Constant. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = GenericsAreGo
| example = GenericsAreGo=TRUE
| datatype = b
| description = Adds a context-menu item to controls and indicators labeled "Generic". This activates an abandoned feature in LabVIEW enabling the creation of "[[Generic VIs]]". If a control marked "generic" is connected to a VI's connector pane, it will automatically change to whatever type is wired to it, and an indicator marked "generic" shows similar behavior with its block diagram terminal. This enables the creation of VI's that can work with literally any type, without needing to use polymorphic VI's. This sounds like it would be useful, '''HOWEVER, you should only use this if you only want to experiment with unreleased features. NI staff have warned against using this in any kind of production code, as it is very buggy, abandoned for a reason, and can corrupt VI's.'''
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2014
| LV2 =
| 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 = ShowHiddenLibraryItems
| example = ShowHiddenLibraryItems=FALSE
| datatype = b
| description = Shows hidden library items (for example when editing a statechart library). <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = showRunAtAnyLoopMenuItem
| example = showRunAtAnyLoopMenuItem=FALSE
| datatype = b
| description = Adds a new menu item to Property and Invoke nodes labeled "Run At Any Loop". When selected, the node turns brown as if a private property or method was selected, even if none are. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SimShowCompanionDiag
| example = SimShowCompanionDiag=FALSE
| datatype = b
| description = Adds a context menu option to the Simulation structure called "Show Companion Diagram", which toggles showing what looks like a "behind-the-scenes" block diagram for the simulation. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SuperSecretPrivateSpecialStuff
| example =SuperSecretPrivateSpecialStuff=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 = useUnicode
| example = useUnicode=FALSE
| datatype = b
| description = Enables Unicode characters in LabVIEW. <ref name="thelvlab">[https://thelvlab.wixsite.com/thelabviewlab/single-post/2017/12/21/All-the-LabVIEWini-Treasures-You-Were-Looking-For All the LabVIEW.ini Treasures You Were Looking For] (The LabVIEW Lab)</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
| OS2 = m
| OS3 = l
| notes = Unicode is not fully supported in LabVIEW. Use with caution!
}}

{{ 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 = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Displays window titles instead of VI names in functions palettes. This key is set by the [[Controls/Functions Palettes options#Formatting|Use window titles in functions palette]] option in the [[Controls/Functions Palettes options|Controls/Functions Palettes]] category of the [[Options dialog]].
| permitted_values = TRUE or FALSE
| default = TRUE
| OS1 = w
| OS2 = m
| OS3 = l
}}

{{ labviewconfigurationkey
| keyname = XNodeDevelopment_LabVIEWInternalTag
| example =XNodeDevelopment_LabVIEWInternalTag=True
| datatype =b
| description =Enables [[XNode|XNodes]] to be edited and created within LabVIEW.
| permitted_values =TRUE or FALSE
| default =FALSE
| OS1 =m
| OS2 =l
| notes =This configuration key does not work on Windows, as it must instead be enabled via the license manager in that version. When enabled, "XNode" will appear in the File->New dialog.
}}

{{ 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
}}

{{ labviewconfigurationkey
| keyname = QuickBold
| example = QuickBold=TRUE
| datatype = b
| description = When editing text (either on the block diagram or the front panel) Ctrl-B allows you to toggle '''bold''' on or off. (When not editing text, Ctrl-B still performs it's normal function: remove broken wires.)
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2013
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

== References ==
<references/>

[[Category:Configuration File|Misc]]

XNodes

2020-09-27T15:29:24Z

Flarn2006:

'''XNodes''' are a technology built into [[LabVIEW 8.0]]+ that allows dynamic edit-time macro support. XNodes are [[Library|Libraries]] that feature several "Ability" [[VI]]s which consist of various events and methods of the XNode.

{{See also|List of XNode Abilities}}

==XNodes used in LabVIEW 8.2==
 
{|cellpadding="2" border="1"
|-
| Class Aggregate Handler? || ([[vi.lib]]\Utility\AggHandler\Cls_AggHandler.xnode)
|-
| Class Grow Array Handler? || ([[vi.lib]]\Utility\XGrowArr-llb\Cls_GrowArr.xnode)
|-
| Regular Expression || ([[vi.lib]]\regexp\Match Regular Expression.xnode)
|-
| Shared Variables || ([[vi.lib]]\variable\varXNode.llb\vi.lib\variable\varXNode.llb\varXNode.xnode)
|-
| Timed Loops || ([[vi.lib]]\Platform\TimedLoop\XDataNode\XDataNode.xnode)
|-
| Database Variant To Data || ([[vi.lib]]\addons\database\_DB Variant To Data\Database Variant To Data.xnode)
|}

== Ability VIs ==
:''Main Article: [[List of XNode Abilities|List of XNode Abilities]].''

== XNodes in Palettes==
XNodes can be added to palettes as if they were plain [[VI]]s; however, the icon
that is displayed in the palette is that stored in the .xnode file and not the image created by the [[Image (XNode Ability)|Image]] Ability vi. It is possible to set the icon in the .xnode file by manually editing the xml file. One way of doing this is to create a LabVIEW library (.lvlib, not .llb) from within LabVIEW and edit the icon for this library. Then making sure that all references to the Xnode are closed, open both the .lvlib file and .xnode file in a text editor and copy across the <Property Name="NI.Lib.Icon"... line.

== Developing XNodes ==
LabVIEW contains functionality to create and edit XNodes as libraries, similar to [[XControl|XControls]]; however, this functionality is not an official part of LabVIEW and is disabled by default. On Linux and macOS, you can enable this functionality in the [[LabVIEW configuration file]], by setting <code>XNodeDevelopment_LabVIEWInternalTag</code> to True.

On Windows, it is not quite as simple, as the functionality is instead enabled via the license manager, requiring an activated license containing the feature <code>LabVIEW_XNodeDevelopment</code>. However, NI does not sell (nor give away) this license, and their server will not activate it for anyone outside of NI. As such, unless you work for NI, enabling XNode development on Windows requires one to bypass the license manager somehow, which may be illegal in some jurisdictions even if you aren't using it for piracy. One alternative is to use another tool to create and edit XNodes, such as hooovahh's [https://lavag.org/files/file/293-xnode-editor/ XNode Editor].

If you have enabled XNode development natively, "XNode" will be available as an option in the File->New dialog. It will appear in the same way as any type of library, and you can add Ability VI's just like one would on an XControl.

==See Also==
*[[External Node]]
*[[XControl]]
*[[VI Scripting]]

[[Category:Xnode]]

Generic VI

2020-09-21T21:51:00Z

Flarn2006: /* History */

A '''Generic VI''' is a VI containing one or more [[Control class/Genericity property|generic]] controls or indicators. Generic VI's are a prototype of what would eventually become the [[Malleable VI]]. As such, they are an unfinished, abandoned technology whose use is not supported by National Instruments, and they are liable to crash LabVIEW and/or corrupt data.

==History==

The first publicly-available Generic VI was published by Aristos Queue in [https://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329?profile.language=en a thread] on the official NI forums. Other than a subsequent update to the VI to correct its randomness, this was the only generic VI published by National Instruments. Both versions had a block diagram password set to prevent the generic controls from being copied to other VI's, and were since taken down regardless.

Development of the Generic VI technology was abandoned, but its concept was later used for the much more stable [[VI Macros]], which finally became Malleable VI's in LabVIEW 2017.

==Creating Generic VI's==

Note: There is no good reason you should be creating a generic VI, unless you are only doing so as a curiosity. For all other purposes, you can use a Malleable VI in much the same way. Furthermore, if you do create any generic VI's, make sure you keep them far away from any VI's you aren't okay with corrupting.

Creating a generic VI is only a matter of placing one or more generic controls or indicators on a VI's front panel, and wiring them to the connector pane. Generic terminals will automatically change to the type wired to them; a generic control can also be placed in an array or cluster to act as "wildcards" in the data type. (For example, a terminal with a generic control inside a non-generic array will accept any array type.)

Generic controls can be obtained either by copying them from an existing Generic VI (such as [[File:Randomize 1D Array nopass.zip]], a passwordless version of Randomize 1D Array) or by making a regular control into a generic one. There are two main ways of doing this:

* Add <code>GenericsAreGo=True</code> to your [[LabVIEW configuration file]]. Right-click a control or indicator, and select the new "Generic" option that appears in the context menu. '''Make sure to remove the configuration file key afterwards, to ensure you don't inadvertently create a Generic VI later on.'''

* Set the [[Control class/Genericity property|Genericity property]] on a control or indicator to True. This property is private, so you will need <code>SuperSecretPrivateSpecialStuff=True</code> in your [[LabVIEW configuration file]].

Generic VI

2020-09-21T21:40:34Z

Flarn2006: /* Creating Generic VI's */ fix bold formatting

A '''Generic VI''' is a VI containing one or more [[Control class/Genericity property|generic]] controls or indicators. Generic VI's are a prototype of what would eventually become the [[Malleable VI]]. As such, they are an unfinished, abandoned technology whose use is not supported by National Instruments, and they are liable to crash LabVIEW and/or corrupt data.

==History==

The first publicly-available Generic VI was published by Aristos Queue in [https://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329?profile.language=en a thread] on the official NI forums. Other than a subsequent update to the VI to correct its randomness, this was the only generic VI published by National Instruments. Both versions had a block diagram password set to prevent the generic controls from being copied to other VI's, and were since taken down regardless.

==Creating Generic VI's==

Note: There is no good reason you should be creating a generic VI, unless you are only doing so as a curiosity. For all other purposes, you can use a Malleable VI in much the same way. Furthermore, if you do create any generic VI's, make sure you keep them far away from any VI's you aren't okay with corrupting.

Creating a generic VI is only a matter of placing one or more generic controls or indicators on a VI's front panel, and wiring them to the connector pane. Generic terminals will automatically change to the type wired to them; a generic control can also be placed in an array or cluster to act as "wildcards" in the data type. (For example, a terminal with a generic control inside a non-generic array will accept any array type.)

Generic controls can be obtained either by copying them from an existing Generic VI (such as [[File:Randomize 1D Array nopass.zip]], a passwordless version of Randomize 1D Array) or by making a regular control into a generic one. There are two main ways of doing this:

* Add <code>GenericsAreGo=True</code> to your [[LabVIEW configuration file]]. Right-click a control or indicator, and select the new "Generic" option that appears in the context menu. '''Make sure to remove the configuration file key afterwards, to ensure you don't inadvertently create a Generic VI later on.'''

* Set the [[Control class/Genericity property|Genericity property]] on a control or indicator to True. This property is private, so you will need <code>SuperSecretPrivateSpecialStuff=True</code> in your [[LabVIEW configuration file]].

Generic VIs

2020-09-21T15:13:34Z

Flarn2006: Redirected page to Generic VI

#REDIRECT [[Generic VI]]

LabVIEW configuration file/Miscellaneous

2020-09-21T15:13:22Z

Flarn2006:

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

{{ labviewconfigurationkey
| keyname = ActiveXMoreContainerOptions
| example = ActiveXMoreContainerOptions=FALSE
| datatype = b
| description = Adds "Persist State To Edit Mode" and "Destroy And Recreate When Run" to the Advanced submenu of an ActiveX container<ref name="lava-18469">[https://lavag.org/topic/18469-i-found-some-more-hidden-ini-keys/ I found some more hidden INI keys (LAVA)]</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
}}

{{ 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 = EnableStrictTypedefConstantConfiguration
| example = EnableStrictTypedefConstantConfiguration=FALSE
| datatype = b
| description = Adds a new context menu item to constants based on strict typedefs called Act as Strict Typedef Constant. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = GenericsAreGo
| example = GenericsAreGo=TRUE
| datatype = b
| description = Adds a context-menu item to controls and indicators labeled "Generic". This activates an abandoned feature in LabVIEW enabling the creation of "[[Generic VIs]]". If a control marked "generic" is connected to a VI's connector pane, it will automatically change to whatever type is wired to it, and an indicator marked "generic" shows similar behavior with its block diagram terminal. This enables the creation of VI's that can work with literally any type, without needing to use polymorphic VI's. This sounds like it would be useful, '''HOWEVER, you should only use this if you only want to experiment with unreleased features. NI staff have warned against using this in any kind of production code, as it is very buggy, abandoned for a reason, and can corrupt VI's.'''
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2014
| LV2 =
| 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 = ShowHiddenLibraryItems
| example = ShowHiddenLibraryItems=FALSE
| datatype = b
| description = Shows hidden library items (for example when editing a statechart library). <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = showRunAtAnyLoopMenuItem
| example = showRunAtAnyLoopMenuItem=FALSE
| datatype = b
| description = Adds a new menu item to Property and Invoke nodes labeled "Run At Any Loop". When selected, the node turns brown as if a private property or method was selected, even if none are. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SimShowCompanionDiag
| example = SimShowCompanionDiag=FALSE
| datatype = b
| description = Adds a context menu option to the Simulation structure called "Show Companion Diagram", which toggles showing what looks like a "behind-the-scenes" block diagram for the simulation. <ref name="lava-18469" />
| permitted_values = TRUE or FALSE
| default = FALSE
}}

{{ 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 = SuperSecretPrivateSpecialStuff
| example =SuperSecretPrivateSpecialStuff=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 = useUnicode
| example = useUnicode=FALSE
| datatype = b
| description = Enables Unicode characters in LabVIEW. <ref name="thelvlab">[https://thelvlab.wixsite.com/thelabviewlab/single-post/2017/12/21/All-the-LabVIEWini-Treasures-You-Were-Looking-For All the LabVIEW.ini Treasures You Were Looking For] (The LabVIEW Lab)</ref>
| permitted_values = TRUE or FALSE
| default = FALSE
| OS1 = w
| OS2 = m
| OS3 = l
| notes = Unicode is not fully supported in LabVIEW. Use with caution!
}}

{{ 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 = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Displays window titles instead of VI names in functions palettes. This key is set by the [[Controls/Functions Palettes options#Formatting|Use window titles in functions palette]] option in the [[Controls/Functions Palettes options|Controls/Functions Palettes]] category of the [[Options dialog]].
| permitted_values = TRUE or FALSE
| default = TRUE
| OS1 = w
| OS2 = m
| OS3 = l
}}

{{ 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
}}

{{ labviewconfigurationkey
| keyname = QuickBold
| example = QuickBold=TRUE
| datatype = b
| description = When editing text (either on the block diagram or the front panel) Ctrl-B allows you to toggle '''bold''' on or off. (When not editing text, Ctrl-B still performs it's normal function: remove broken wires.)
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2013
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

== References ==
<references/>

[[Category:Configuration File|Misc]]

Generic VI

2020-09-21T04:25:59Z

Flarn2006: Created page with "A '''Generic VI''' is a VI containing one or more generic controls or indicators. Generic VI's are a prototype of what would eventually b..."

A '''Generic VI''' is a VI containing one or more [[Control class/Genericity property|generic]] controls or indicators. Generic VI's are a prototype of what would eventually become the [[Malleable VI]]. As such, they are an unfinished, abandoned technology whose use is not supported by National Instruments, and they are liable to crash LabVIEW and/or corrupt data.

==History==

The first publicly-available Generic VI was published by Aristos Queue in [https://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329?profile.language=en a thread] on the official NI forums. Other than a subsequent update to the VI to correct its randomness, this was the only generic VI published by National Instruments. Both versions had a block diagram password set to prevent the generic controls from being copied to other VI's, and were since taken down regardless.

==Creating Generic VI's==

Note: There is no good reason you should be creating a generic VI, unless you are only doing so as a curiosity. For all other purposes, you can use a Malleable VI in much the same way. Furthermore, if you do create any generic VI's, make sure you keep them far away from any VI's you aren't okay with corrupting.

Creating a generic VI is only a matter of placing one or more generic controls or indicators on a VI's front panel, and wiring them to the connector pane. Generic terminals will automatically change to the type wired to them; a generic control can also be placed in an array or cluster to act as "wildcards" in the data type. (For example, a terminal with a generic control inside a non-generic array will accept any array type.)

Generic controls can be obtained either by copying them from an existing Generic VI (such as [[File:Randomize 1D Array nopass.zip]], a passwordless version of Randomize 1D Array) or by making a regular control into a generic one. There are two main ways of doing this:

* Add <code>GenericsAreGo=True</code> to your [[LabVIEW configuration file]]. Right-click a control or indicator, and select the new "Generic" option that appears in the context menu. '''Make sure to remove the configuration file key afterwards, to ensure you don't inadvertently create a Generic VI later on.''

* Set the [[Control class/Genericity property|Genericity property]] on a control or indicator to True. This property is private, so you will need <code>SuperSecretPrivateSpecialStuff=True</code> in your [[LabVIEW configuration file]].

File:Randomize 1D Array nopass.zip

2020-09-21T04:12:28Z

Flarn2006:

== Summary ==
The "Randomize 1D Array" [[Generic VI]], created by Aristos Queue. [https://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329?profile.language=en Originally published here.]

Note: there were two versions of the VI published; I'm pretty sure this is the second version with its randomness corrected. This VI has additionally been modified in that its block diagram password has been removed. I am not sure whether I still have a copy of the version with the password.

File:Randomize 1D Array nopass.zip

2020-09-21T04:08:58Z

Flarn2006: The "Randomize 1D Array" Generic VI, created by Aristos Queue. [https://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329?profile.language=en Originally published here.] Note:...

Control class/Genericity property

2020-09-21T03:41:27Z

Flarn2006: /* Uses */

{{VIServerProperty
| classid = 6
| propertyid = 633203C
| scope=private
| dataname = Genericity
| shortname = Genericity
| longname = Genericity
| datatypeimage = Boolean.png
| datatype = Boolean
| propertynodeimage = Control-Genericity.png
| permissions = Read/Write
|}}
{{TOCright}}

== Uses ==
When True, the control or indicator will change to match the type of whatever data is wired to it, resulting in behavior similar to a [[Malleable VI]]. A VI containing a control or indicator with this property set to True becomes a [[Generic VI]]. Do not use this property. Generic VI's are an unfinished, abandoned feature of LabVIEW which is liable to cause crashes and corruption. Use a Malleable VI instead.

== 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 wiki pages that would also help.}}

== External Links ==
{{ambox|text=Add links to external resources that would also help.}}
[[Category:VI Scripting Property]]

[[Category:Private Property]]
[[Category:VI Server Property]]

VI class/Is Generic property

2020-09-21T03:35:45Z

Flarn2006: /* Uses */

{{VIServerProperty
| classid = 2
| propertyid = 2A3
| scope=private
| dataname = IsGeneric
| shortname = IsGeneric
| longname = Is Generic
| datatypeimage = Boolean.png
| datatype = Boolean
| propertynodeimage = VI-Is Generic.png

|}}
{{TOCright}}

== Uses ==
True if the VI is a [[Generic VI]].

== 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 wiki pages that would also help.}}

== External Links ==
{{ambox|text=Add links to external resources that would also help.}}
[[Category:Private Property]]

[[Category:VI Server Property]]

Resource Container

2020-09-20T17:24:49Z

Flarn2006: Added BDHT/FPHT/BDHX/FPHX

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHT
|Block Diagram Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|FPHT
|Front Panel Heap Text
|Used when [[Heap storage format]] is set to Verbose Tagged Text.
|-
|BDHX
|Block Diagram Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|FPHX
|Front Panel Heap XML
|Used when [[Heap storage format]] is set to XML.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|This section is responsible for the "operator overloading" effect that the built-in matrix typedefs have. Copying it from RealMatrix.ctl to a new typedef, and then wiring an instance of that new typedef to an Add node, causes the Add node to become its matrix variant, as occurs with the matrix typedef. This section is most likely used for other purposes as well.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

Resource Container

2020-09-20T17:19:52Z

Flarn2006: /* Known Resources */ Added an observed effect of VITS (operator overloading)

'''Resource Container''' file format is a most often used file format within LabVIEW ecosystem. It is a proprietary binary format defined by [[National Instruments]] and used in both [[LabVIEW]] and [https://en.wikipedia.org/wiki/LabWindows/CVI LabWindows/CVI]. The format is strongly inspired by [https://en.wikipedia.org/wiki/Resource_fork Mac OS Resource Fork format], as LabVIEW was originally created for that platform, and ported to other OSes later, at [[LabVIEW 2.0|version 2.5]].

The format is a container, storing a group of '''Resources'''. Resources have '''4-character identifier''' assigned, and the 4-character identifier for the whole container is ''RSRC''. Most files used by LabVIEW have that ''RSRC'' format, only the specific '''Resources''' stored inside are different. The files with that header include [[VI File Extension|''*.vi'']], [[CTL File Extension|''*.ctl'']], [[MNU File Extension|''*.mnu'']], [[LLB File Extension|''*.llb'']], [[DLOG File Extension|''*.dlog'']], [[CTT File Extension|''*.ctt'']], [[VIT File Extension|''*.vit'']], [[UIR File Extension|''*.uir'']], and many created with, or internally used by, LabVIEW.

The resources stored within have their identifiers often identical to those in ''Resource fork'' format, but many new ones are also introduced. Some resources have multiple variations, as their structure changed between versions of [[LabVIEW]].

==Known Resources==

Below a few resources are listed. Note that the text names given for them are mostly informed guesses.

{| class="wikitable"
! Resource ID
! Long Name
! Description
|-
|MUID
|Map Unique Identifier
|
|-
|FPSE
|Front Panel Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Front Panel Heap divided by 10. See also: ''BDSE''.
|-
|FPTD
|Front Panel Type for DataLog
|
|-
|BDSE
|Block Diagram Size Estimate
|Optional resource which can be used to optimize memory allocation when loading the VI file. Contains one integer value, which seem be amount of tags within Block Diagram Heap divided by 10. See also: ''FPSE''.
|-
|FLAG
|Integer flags
|
|-
|CONP
|Connector Port Type Map
|
|-
|CPTM
|Connector Port Type Map
|
|-
|CPC2
|Connector Port Content Type v2
|
|-
|CPCT
|Connector Port Content Type
|
|-
|CPD2
|Connector Port DI v2
|
|-
|CPDI
|Connector Port DI
|
|-
|DLGH
|Dialog HTML
|
|-
|ERRH
|Error HTML
|
|-
|HLPT
|Help Tag
|
|-
|MItm
|M. Item
|
|-
|NODH
|NOD HTML
|
|-
|NOEG
|NOEG String
|
|-
|STRG
|String description
|
|-
|TITL
|Title of the file
|
|-
|STR
|Short String / Input definition?
|
|-
|CPST
|C. P. Strings
|
|-
|DNm#
|D. Name Strings List
|
|-
|HDb#
|Help Database item
|
|-
|LST#
|Short Strings List
|
|-
|STR#
|Short Strings List
|
|-
|FDFL
|FDFL Strings
|
|-
|LIfp
|LinkObj Refs for Front Panel
|
|-
|LIbd
|LinkObj Refs for Block diagram
|
|-
|LIds
|LinkObj Refs for Data Space
|
|-
|LIvi
|LinkObj Refs for VI
|
|-
|DFDS
|Default Fill of Data Space
|
|-
|GCDI
|
|
|-
|BFAL
|
|
|-
|CGRS
|Conglomerate Resource
|
|-
|CPMp
|Connection Points Map
|
|-
|DLDR
|DL Data Record
|
|-
|DLLP
|DL Local Path
|
|-
|FTAB
|Font Table
|
|-
|HIST
|Changes History
|
|-
|HLPP
|Help Path
|
|-
|LPTH
|L. Path
|
|-
|HLPW
|Help Website URL
|
|-
|SCSR
|Syntax Checker Digest
|
|-
|DTHP
|Data Types for Heap
|
|-
|DSTM
|Data Space Type Map
|Stores table of [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the VI file. Used in LV 7.1 and older.
|-
|TM80
|Data Space Type Map LV8.0+
|Stores table of references to [[Type descriptor|Type descriptors]] which make up [[Data Space]] of the [[VI|VI file]]. The actual definitions of '''TD'''s are stored in ''VCTP'' block. Used in [[LabVIEW 8|LV 8.0]] and newer.
|-
|LVIN
|LabView Instrument
|General information about a saved [[VI|VI file]]; definitely used in [[LabVIEW 4.0|LV 4.0]] and older, was replaced by ''LVSR'' at some point.
|-
|LVSR
|LabView Save Record
|General information about a saved [[VI|VI file]]; replaced ''LVIN'' resource somewhere before [[LabVIEW 6i|LV 6.0]]. The size of this resource increases with [[LabVIEW Versions|LV version]], but old data is always kept at the same offset (new fields are only added at end).
|-
|vers
|Version block
|Stores version of LV used to create the RSRC file.
|-
|PNGI
|PNG Image
|Stores a bitmap picture in [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG format].
|-
|MNGI
|MNG Image
|While PNGs become quite popular, their animated counterpart, [https://en.wikipedia.org/wiki/Multiple-image_Network_Graphics MNG format], never really caught on.
|-
|ICON
|Icon 32x32 1bpp
|
|-
|ICN#
|Icon Large Double 32x64 1bpp
|Usually used to store one icon in two versions (ie. disabled and active).
|-
|ics#
|Icon Small 16x16 1bpp
|
|-
|CURS
|Cursor 16x34 1bpp
|Usually used to store one cursor in two versions (ie. disabled and active).
|-
|ics4
|Icon Small 16x16 4bpp
|
|-
|icl4
|Icon Large 32x32 4bpp
|
|-
|ics8
|Icon Small 16x16 8bpp
|
|-
|icl8
|Icon Large 32x32 8bpp
|
|-
|BDPW
|Block Diagram Password
|
|-
|LIBN
|Library Names
|
|-
|LVzp
|LabView Zipped Program tree
|A whole application compressed to ZIP file.
|-
|PRT
|Print settings
|
|-
|BNID
|B. N. Identifier
|
|-
|CNST
|Constant Node UID set
|
|-
|LPIN
|Loop Invariant Node UID set
|
|-
|NUID
|N. U. Identifier
|
|-
|SUID
|S. U. Identifier
|
|-
|VPDP
|VI Primitive Dependency Flags
|
|-
|BDHP
|Block Diagram Heap
|First version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHP
|Front Panel Heap
|First version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHb
|Block Diagram Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHb
|Front Panel Heap ver b
|Second version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|BDHc
|Block Diagram Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Block Diagram.
|-
|FPHc
|Front Panel Heap ver c
|Third version of [[Heap storage format]], used to store components placed on Front Panel.
|-
|RTSG
|Runtime Signature Guid
|
|-
|GCPR
|Generated Code Profiler settings
|
|-
|UCRF
|Uncompressed Resource File
|Used when files are added to ''RSRC'', ie. within ''*.llb'' files.
|-
|CPRF
|'Comp' Compressed Resource File
|Used when files are added to ''RSRC''; very basic mask based compression.
|-
|ZCRF
|ZLib Compressed Resource File
|Used when files are added to ''RSRC''; uses compression algorithm from popular Z-Lib library.
|-
|DLG3
|Dialog Resource File
|
|-
|VCTP
|VI Consolidated Data Types
|Introduced in LV 8.0, stores all [[Type descriptor|Type descriptors]] used within the file.
|-
|VICD
|Virtual Instrument Compiled Data / VI Code
|Contains the machine code generated by LLVM compiler.
|-
|VITS
|Virtual Instrument Tag Strings
|This section is responsible for the "operator overloading" effect that the built-in matrix typedefs have. Copying it from RealMatrix.ctl to a new typedef, and then wiring an instance of that new typedef to an Add node, causes the Add node to become its matrix variant, as occurs with the matrix typedef. This section is most likely used for other purposes as well.
|}

[[Category:LabVIEW file extensions|other files]]
[[Category:LabVIEW internals]]

Project Provider Framework

2014-10-01T02:40:55Z

Flarn2006:

The Project Provider Framework is a semi-NI-internal API used to extend LabVIEW in various ways, mostly relating to the project interface. In order to create plugins for this framework, you need to create an INI file in ''(your LabVIEW installation directory)''/resource/Framework/Providers/GProviders, and said INI file needs to be signed, presumably by NI or an approved developer for the framework. The method by which this signature (actually a checksum, as there is no separate private key) is calculated has been reverse-engineered, however. Until more information about this framework has been publicly documented, this page shall serve as an explanation on the signature's calculation. (See the bottom of this page for a link to a tool that automatically calculates the required signature.)

First, take the ''values'' (not the keys) in the INI file in order, and concatenate them. Only include the values for keys in this list (rule of thumb: string values, not Boolean or numeric values, and don't include the Signature key of course):

* "InterfaceVersion"
* "LicenseRestrictions"
* "LicenseVersion"
* "LicenseName"
* "Alias"
* "SupportedType"
* "SupportedInterface"
* "CreateNewWizardHost"
* "BuildInterfaceVI"
* "DeployInterfaceVI"
* "SourceControlInterfaceVI"
* "CreateNewWizardInterfaceVI"
* "GlobalItemInterfaceVI"
* "ProviderInterfaceVI"
* "ItemInterfaceVI"

Do not include spaces or any other types of delimiters between values in the concatenated string. Take the MD5 hash of this string, and apply the following substitution cipher to each of the digits:

Change: 0123456789ABCDEF
To: T3C5K7W9SBNRJLX2

Finally, for each pair of two consecutive digits, switch them. For example, CRTTR3X7 would become RCTT3R7X. You now have your signature!

==See also==
* [http://lavag.org/topic/18545-i-have-taken-the-first-step-towards-unofficially-opening-up-the-project-provider-framework/ Forum post announcing the discovery of the algorithm]
* [http://lavag.org/index.php?app=core&module=attach&section=attach&attach_id=9546 Open-source tool to automatically sign an INI file]

Project Provider Framework

2014-10-01T02:35:37Z

Flarn2006: Created page with "The Project Provider Framework is a semi-NI-internal API used to extend LabVIEW in various ways, mostly relating to the project interface. In order to create plugins for this fra..."

The Project Provider Framework is a semi-NI-internal API used to extend LabVIEW in various ways, mostly relating to the project interface. In order to create plugins for this framework, you need to create an INI file in ''(your LabVIEW installation directory)''/resource/Framework/Providers/GProviders, and said INI file needs to be signed, presumably by NI or an approved developer for the framework. The method by which this signature (actually a checksum, as there is no separate private key) is calculated has been reverse-engineered, however. Until more information about this framework has been publicly documented, this page shall serve as an explanation on the signature's calculation. (See the bottom of this page for a link to a tool that automatically calculates the required signature.)

First, take the ''values'' (not the keys) in the INI file in order, and concatenate them. Only include the values for keys in this list (rule of thumb: string values, not Boolean or numeric values, and don't include the Signature key of course):

* "InterfaceVersion"
* "LicenseRestrictions"
* "LicenseVersion"
* "LicenseName"
* "Alias"
* "SupportedType"
* "SupportedInterface"
* "CreateNewWizardHost"
* "BuildInterfaceVI"
* "DeployInterfaceVI"
* "SourceControlInterfaceVI"
* "CreateNewWizardInterfaceVI"
* "GlobalItemInterfaceVI"
* "ProviderInterfaceVI"
* "ItemInterfaceVI"

Do not include spaces or any other types of delimiters between values in the concatenated string. Take the MD5 hash of this string, and apply the following substitution cipher to each of the digits:

Change: 0123456789ABCDEF
To: T3C5K7W9SBNRJLX2

Finally, for each pair of two consecutive digits, switch them. For example, CRTTR357 would become RCTT3R75. You now have your signature!

==See also==
* [http://lavag.org/topic/18545-i-have-taken-the-first-step-towards-unofficially-opening-up-the-project-provider-framework/ Forum post announcing the discovery of the algorithm]
* [http://lavag.org/index.php?app=core&module=attach&section=attach&attach_id=9546 Open-source tool to automatically sign an INI file]

Talk:Numeric

2014-09-09T06:05:16Z

Flarn2006: Created page with "==Nobody remembers the value?== I know it by heart, at least for I32. 2,147,483,647. ~~~~"

==Nobody remembers the value?==
I know it by heart, at least for I32. 2,147,483,647. [[User:Flarn2006|Flarn2006]] 02:05, 9 September 2014 (EDT)

LabVIEW configuration file/Miscellaneous

2014-09-02T05:13:55Z

Flarn2006:

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 = GenericsAreGo
| example = GenericsAreGo=TRUE
| datatype = b
| description = Adds a context-menu item to controls and indicators labeled "Generic". This activates an abandoned feature in LabVIEW enabling the creation of "Generic VIs". If a control marked "generic" is connected to a VI's connector pane, it will automatically change to whatever type is wired to it, and an indicator marked "generic" shows similar behavior with its block diagram terminal. This enables the creation of VI's that can work with literally any type, without needing to use polymorphic VI's. This sounds like it would be useful, '''HOWEVER, you should only use this if you only want to experiment with unreleased features. NI staff have warned against using this in any kind of production code, as it is very buggy, abandoned for a reason, and can corrupt VI's.'''
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2014
| LV2 =
| 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 = SuperSecretPrivateSpecialStuff
| example =SuperSecretPrivateSpecialStuff=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
}}

{{ labviewconfigurationkey
| keyname = QuickBold
| example = QuickBold=TRUE
| datatype = b
| description = When editing text (either on the block diagram or the front panel) Ctrl-B allows you to toggle '''bold''' on or off. (When not editing text, Ctrl-B still performs it's normal function: remove broken wires.)
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 2013
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}

[[Category:Configuration File|Misc]]

Talk:Linker.Read info from file

2013-01-20T05:33:03Z

Flarn2006: Forgot to sign my message.

==Are you sure this is a private method?==
In the image on the article, the invoke node is light blue. This means it requires scripting to be enabled, but it's not private. If it was private, the node would be brown. [[User:Flarn2006|Flarn2006]] 00:33, 20 January 2013 (EST)

Talk:Linker.Read info from file

2013-01-20T05:32:42Z

Flarn2006: Created page with "==Are you sure this is a private method?== In the image on the article, the invoke node is light blue. This means it requires scripting to be enabled, but it's not private. If it..."

File:Fake Exec State.png

2013-01-20T00:13:18Z

Flarn2006: uploaded a new version of "File:Fake Exec State.png"

An example use of the private method [[VI.Fake Exec State]] which, when called, will make the VI appear to stop while still running.

File:Fake Exec State.png

2013-01-19T23:56:42Z

Flarn2006: An example use of the private method VI.Fake Exec State which, when called, will make the VI appear to stop while still running.

An example use of the private method [[VI.Fake Exec State]] which, when called, will make the VI appear to stop while still running.

User:Flarn2006/Sandbox

2013-01-17T06:17:38Z

Flarn2006:

A generic VI is any VI which contains generic controls and/or indicators. Generic controls and indicators automatically change to match whatever type is wired to them, similar to polymorphic VIs. Unlike polymorphic VIs, however, a generic VI can accept ''any'' type, and all its code needs only to be implemented once. While this sounds quite useful, '''the use of generic VIs has been officially condemned by NI, as they are very likely to cause serious problems.'''

==Origin==
The first generic VI was published<ref name="r1da">[http://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329]</ref> by Aristos Queue on June 24, 2010. Randomize 1D Array.vi, the aforementioned generic VI, accepted an array of any type, and would output the same array except in a different, pseudorandom order. Aristos later announced that "the beta test [was] finished; the VIs are no longer available for download because instabilities [had] been identified."<ref name="r1da" /> The VI is still available, however, through the Internet Archive's Wayback Machine.<ref>http://web.archive.org/web/20100811000744/http://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329</ref>

==Creating generic VIs==
Although Randomize 1D Array.vi was password protected, the control and indicator were copied anyway, and posted to the LAVA forums by flarn2006.<ref>[http://lavag.org/topic/15870-create-your-own-generic-vi-like-randomize-1d-array/]</ref> This allowed the creation of custom generic VIs.
If a generic control or indicator is put in an array, the terminal will only accept arrays of that dimension, except any array type can be used. Similarly, a generic control or indicator can be placed in a cluster, and it will only accept that cluster type, except with any type in place of the generic control.

==Disclaimer==
'''As was mentioned before, generic VIs are NOT supported in any way by National Instruments. Due to several issues, they are not under any circumstances to be used in any production code. The information on this page is intended only for exploration and experimentation with a private feature of LabVIEW, and not for use in any serious work.'''

==External Links==
* [Original thread on NI's official forums about generic VIs http://forums.ni.com/t5/LabVIEW-Developers-Feature/Now-available-for-download-quot-Randomize-1D-Array-vi-quot-that/td-p/1159329]
* [LAVA thread detailing creation of generic VIs http://lavag.org/topic/15870-create-your-own-generic-vi-like-randomize-1d-array/]

==Notes==
{{reflist}}

User:Flarn2006/Sandbox

2013-01-17T05:57:22Z

Flarn2006: Created page with "A generic VI is any VI which contains generic controls and/or indicators. Generic controls and indicators automatically change to match whatever type is wired to them, similar to..."