Jump to content

LabVIEW configuration file/Miscellaneous: Difference between revisions

From LabVIEW Wiki
← Older edit
VisualWikitext
mNo edit summary
Dnatt (talk | contribs)
43 edits
m Removed bad link to ni.com (I couldn't find a replacement link)
 
(36 intermediate revisions by 10 users not shown)
Line 1: Line 1:
{{LabVIEW configuration back}}
This is a list of Miscellaneous LabVIEW ini File settings. {{TOCright}}
[[Category:Development Environment]]
 
This is a list of Miscellaneous LabVIEW ini File settings.
{{ 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 =None
}}
 
{{ 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
{{ labviewconfigurationkey
Line 13: Line 231:
| OS1 = w
| OS1 = w
}}
}}
== BldApp.RemovePolyVIsandTypedefs ==
Example: <code>BldApp.RemovePolyVIsandTypedefs=FALSE</code><br/>
Description: Setting this to <code>TRUE</code> stops the LabVIEW Application Builder from agressively removing polymorphic VIs and typedefs that it thinks are not required<br/>
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
Default Value: <code>TRUE</code><br/>
LabVIEW Versions: 7.x<br/>
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
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.<br/>


== cleanupVisa ==
{{ labviewconfigurationkey
Example: <code>coerceFromVariant=TRUE</code><br/>
| keyname = openInRun
Description: Force variants to automatically coerce to any data type that they are connected to<br/>
| example =openInRun=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description =When opening VIs in the development environment, open them in ''run mode''
Default Value: <code>FALSE</code><br/>
| permitted_values =TRUE or FALSE
LabVIEW Versions: 7.x, 8.x<br/>
| default =FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 3
Notes: Tread carefully, as using this function removes coercion notifivation, and does not useerror handling<br/>
| 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
}}


== cleanupVisa ==
{{ labviewconfigurationkey
Example: <code>cleanupVisa=TRUE</code><br/>
| keyname = useUnicode
Description: Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI<br/>
| example = useUnicode=FALSE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype = b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| 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>
Default Value: <code>FALSE</code><br/>
| permitted_values = TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default = FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| OS1 = w
Notes: None<br/>
| OS2 = m
| OS3 = l
| notes = Unicode is not fully supported in LabVIEW. Use with caution!
}}


== dropThroughClicks ==
{{ labviewconfigurationkey
Example: <code>dropThroughClicks=FALSE</code><br/>
| keyname = userVIsAppearFirst
Description: Allow drop-through clicks<br/>
| example =userVIsAppearFirst=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description =Makes the user VIs appear first in the tool menu
Default Value: <code>TRUE</code><br/>
| permitted_values =TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default =FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 6
Notes: None<br/>
| LV2 = 7
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Unfortunately this option no longer works in LabVIEW versions 8+.
}}


== ExternalNodesEnabled ==
{{ labviewconfigurationkey
Example: <code>ExternalNodesEnabled=FALSE</code><br/>
| keyname = viTitleInPalettes
Description: Enables use of [[External Nodes]]<br/>
| example = viTitleInPalettes=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype = b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| 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]].
Default Value: 6.x?, 7.x: <code>TRUE</code> 8.x: <code>FALSE</code>?<br/>
| permitted_values = TRUE or FALSE
LabVIEW Versions: 6.x?, 7.x, 8.x<br/>
| default = TRUE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| OS1 = w
Notes: None<br/>
| OS2 = m
| OS3 = l
}}


== ExternalNodeDebugging ==
{{ labviewconfigurationkey
Example: <code>ExternalNodeDebugging=FALSE</code><br/>
| keyname = XNodeDevelopment_LabVIEWInternalTag
Description: Shows External Nodes for what they are: sequence diagrams<br/>
| example =XNodeDevelopment_LabVIEWInternalTag=True
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description =Enables [[XNode|XNodes]] to be edited and created within LabVIEW.
Default Value: <code>FALSE</code><br/>
| permitted_values =TRUE or FALSE
LabVIEW Versions: 7.x, 8.x<br/>
| default =FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| OS1 =m
Notes: None<br/>
| 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.
}}


== hotMenus ==
{{ labviewconfigurationkey
Example: <code>hotMenus=FALSE</code><br/>
| keyname = XNodeWizardMode
Description: Use hot menus<br/>
| example =XNodeWizardMode=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description =Allows contextual menus on [[XNodes]] to facilitate debugging
Default Value: <code>TRUE</code><br/>
| permitted_values =TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default =FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 8
Notes: None<br/>
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}


== openInRun ==
{{ labviewconfigurationkey
Example: <code>openInRun=TRUE</code><br/>
| keyname = MaxGSWRecentProjects
Description: When opening VIs in the development environment, open them in ''run mode''<br/>
| example =MaxGSWRecentProjects=10
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =i
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description =Allows more projects to be added to the Getting Started Window
Default Value: <code>FALSE</code><br/>
| permitted_values = 1 to 10
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default = 2
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 2009
Notes: None<br/>
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}


== readOnlyLock ==
Example: <code>readOnlyLock=TRUE</code><br/>
Description: Treat read-only VIs as locked<br/>
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
Default Value: <code>FALSE</code><br/>
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
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<br/>


== showBDConstName ==
{{ labviewconfigurationkey
Example: <code>showBDConstName=TRUE</code><br/>
| keyname = operateCursorRunningVIs
Description: Show auto-constant labels<br/>
| example = operateCursorRunningVIs=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description =Changes the default cursor on running VIs to its behavior prior to LabVIEW 2012
Default Value: <code>FALSE</code><br/>
| permitted_values =TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default = FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 2012
Notes: None<br/>
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}


== ShowTipStrings ==
{{ labviewconfigurationkey
Example: <code>ShowTipStrings=FALSE</code><br/>
| keyname = useNewProjWiz
Description: Display Tip Strips during execution<br/>
| example = useNewProjWiz =FALSE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype =b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| 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.
Default Value: <code>TRUE</code><br/>
| permitted_values =TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default = TRUE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]]<br/>
| LV1 = 2012
Notes: None<br/>
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}


== skipNavigatorDialog ==
{{ labviewconfigurationkey
Example: <code>skipNavigatorDialog=TRUE</code><br/>
| keyname = QuickBold
Description: Skip the navigation dialog on development environment launch<br/>
| example = QuickBold=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype = b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| 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.)
Default Value: <code>FALSE</code><br/>
| permitted_values = TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default = FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 2013
Notes: None<br/>
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}


== suppressFileDlgForMissingVIs ==
{{ labviewconfigurationkey
Example: <code>suppressFileDlgForMissingVIs=TRUE</code><br/>
| keyname = ShowConsoleForPythonNode
Description: Suppresses the file dialog for when loading a VI that has missing SubVIs<br/>
| example = ShowConsoleForPythonNode=TRUE
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
| datatype = b
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
| description = Shows the output from Python when a Python Node executes.<ref name="ni-ShowConsoleForPythonNode"/>
Default Value: <code>FALSE</code><br/>
| permitted_values = TRUE or FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
| default = FALSE
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
| LV1 = 2018 and later
Notes: None<br/>
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes =
}}


== useNativeFileDialog ==
== References ==
Example: <code>useNativeFileDialog=FALSE</code><br/>
<references>
Description: Use the OS native file dialogs<br/>
<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>
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
</references>
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
Default Value: <code>TRUE</code><br/>
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x<br/>
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
Notes: None<br/>


== XNodeWizardMode ==
[[Category:Configuration File|Misc]]
Example: <code>XNodeWizardMode=FALSE</code><br/>
Description: Allows contextual menus on [[XNodes]] to facilitate debugging<br/>
Datatype: <FONT COLOR=#008000>Boolean</FONT><br/>
Permitted Values: <code>TRUE</code> or <code>FALSE</code><br/>
Default Value: <code>FALSE</code><br/>
LabVIEW Versions: 8.x<br/>
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/>
Notes: None<br/>

Latest revision as of 18:30, 21 October 2022

This is a list of Miscellaneous LabVIEW ini File settings.

ActiveXMoreContainerOptions

Example ActiveXMoreContainerOptions=FALSE
Description Adds "Persist State To Edit Mode" and "Destroy And Recreate When Run" to the Advanced submenu of an ActiveX container[1]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

Notes

BldApp.RemovePolyVIsandTypedefs

Example BldApp.RemovePolyVIsandTypedefs=FALSE
Description Setting this to FALSE stops the LabVIEW Application Builder from aggressively removing polymorphic VIs and typedefs that it thinks are not required
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

7.x

OS's Supported

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.

coerceFromVariant

Example coerceFromVariant=TRUE
Description Force variants to automatically coerce to any data type that they are connected to
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

7.x , 8.x

OS's Supported

Notes Tread carefully, as using this function removes coercion notification, and does not use error handling

cleanupVisa

Example cleanupVisa=TRUE
Description Automatically close VISA sessions - do not require the use of the VISA Close VI
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

defaultConPane

Example defaultConPane=4833
Description Sets the default Connector pane layout for new VIs
Datatype I32
Permitted Values
Default Value (4815)
LabVIEW Versions

8.x

OS's Supported

Notes None

dropThroughClicks

Example dropThroughClicks=FALSE
Description Allow drop-through clicks
Datatype Integer
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

4.x , 5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

EnableStrictTypedefConstantConfiguration

Example EnableStrictTypedefConstantConfiguration=FALSE
Description Adds a new context menu item to constants based on strict typedefs called Act as Strict Typedef Constant. [1]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

Notes

ExternalNodesEnabled

Example ExternalNodesEnabled=FALSE
Description Enables use of External Nodes
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value 6.x?, 7.x: TRUE 8.x: FALSE
LabVIEW Versions

6.x? , 7.x , 8.x

OS's Supported

Notes None

ExternalNodeDebugging

Example ExternalNodeDebugging=FALSE
Description Shows External Nodes for what they are: sequence diagrams
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

7.x , 8.x

OS's Supported

Notes None

GenericsAreGo

Example GenericsAreGo=TRUE
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.
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

2014

OS's Supported

Notes None

hotMenus

Example hotMenus=FALSE
Description Use hot menus
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

4.x , 5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

MaxHelpDescLength

Example MaxHelpDescLength=8000
Description Maximum number of characters that will be displayed before truncation in the Context Help
Datatype Integer
Permitted Values
Default Value 8000
LabVIEW Versions

8.x

OS's Supported

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

MRUFolders

Example MRUFolders=TRUE
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.
Datatype Boolean
Permitted Values TRUE, FALSE
Default Value FALSE
LabVIEW Versions

8.2

OS's Supported

Notes

openInRun

Example openInRun=TRUE
Description When opening VIs in the development environment, open them in run mode
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

3.x , 4.x , 5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

readOnlyLock

Example readOnlyLock=TRUE
Description Treat read-only VIs as locked
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

5.x , 6.x , 7.x , 8.x

OS's Supported

Notes It is important to set this to TRUE 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

showBDConstName

Example showBDConstName=TRUE
Description Show auto-constant labels
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

4.x , 5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

ShowHiddenLibraryItems

Example ShowHiddenLibraryItems=FALSE
Description Shows hidden library items (for example when editing a statechart library). [1]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

Notes

showNoNavDialog

Example showNoNavDialog=TRUE
Description Prevents the "Getting Started Window" dialog from appearing
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

8.x

OS's Supported

Notes Source: NI Knowledge Base ( http://digital.ni.com/public.nsf/allkb/841B934909D863C886256F62006AC243?OpenDocument )

showRunAtAnyLoopMenuItem

Example showRunAtAnyLoopMenuItem=FALSE
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. [1]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

Notes

ShowTipStrings

Example ShowTipStrings=FALSE
Description Display Tip Strips during execution
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

4.x , 5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

SimShowCompanionDiag

Example SimShowCompanionDiag=FALSE
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. [1]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

Notes

skipNavigatorDialog

Example skipNavigatorDialog=TRUE
Description Skip the navigation dialog on development environment launch
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

SuperSecretPrivateSpecialStuff

Example SuperSecretPrivateSpecialStuff=TRUE
Description Exposes private properties, method and events in the IDE
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

8.x

OS's Supported

Notes Not supported by NI, this is not a scripting method.

suppressFileDlgForMissingVIs

Example suppressFileDlgForMissingVIs=TRUE
Description Suppresses the file dialog for when loading a VI that has missing SubVIs
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

useNativeFileDialog

Example useNativeFileDialog=FALSE
Description Use the OS native file dialogs
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

4.x , 5.x , 6.x , 7.x , 8.x

OS's Supported

Notes None

useUnicode

Example useUnicode=FALSE
Description Enables Unicode characters in LabVIEW. [2]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

Notes Unicode is not fully supported in LabVIEW. Use with caution!

userVIsAppearFirst

Example userVIsAppearFirst=TRUE
Description Makes the user VIs appear first in the tool menu
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

6.x , 7.x

OS's Supported

Notes Unfortunately this option no longer works in LabVIEW versions 8+.

viTitleInPalettes

Example viTitleInPalettes=TRUE
Description Displays window titles instead of VI names in functions palettes. This key is set by the Use window titles in functions palette option in the Controls/Functions Palettes category of the Options dialog.
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

OS's Supported

Notes

XNodeDevelopment_LabVIEWInternalTag

Example XNodeDevelopment_LabVIEWInternalTag=True
Description Enables XNodes to be edited and created within LabVIEW.
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

OS's Supported

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.

XNodeWizardMode

Example XNodeWizardMode=TRUE
Description Allows contextual menus on XNodes to facilitate debugging
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

8.x

OS's Supported

Notes None

MaxGSWRecentProjects

Example MaxGSWRecentProjects=10
Description Allows more projects to be added to the Getting Started Window
Datatype Integer
Permitted Values 1 to 10
Default Value 2
LabVIEW Versions

2009

OS's Supported

Notes None


operateCursorRunningVIs

Example operateCursorRunningVIs=TRUE
Description Changes the default cursor on running VIs to its behavior prior to LabVIEW 2012
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

2012

OS's Supported

Notes None

useNewProjWiz

Example useNewProjWiz =FALSE
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.
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value TRUE
LabVIEW Versions

2012

OS's Supported

Notes None

QuickBold

Example QuickBold=TRUE
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.)
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

2013

OS's Supported

Notes

ShowConsoleForPythonNode

Example ShowConsoleForPythonNode=TRUE
Description Shows the output from Python when a Python Node executes.[3]
Datatype Boolean
Permitted Values TRUE or FALSE
Default Value FALSE
LabVIEW Versions

2018 and later

OS's Supported

Notes

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 I found some more hidden INI keys (LAVA)
  2. ↑ All the LabVIEW.ini Treasures You Were Looking For (The LabVIEW Lab)
  3. ↑ Improved Python Support (LabVIEW 2021 Public Beta) by Christina Rogers
Retrieved from "https://labviewwiki.org/w/index.php?title=LabVIEW_configuration_file/Miscellaneous&oldid=31869"