LabVIEW's hidden INI Keys

LabVIEW

There are some “hidden” INI keys available in LabVIEW, which I often forgot

Run At Any Loop #

showRunAtAnyLoopMenuItem=True

Allow to open references and run not only in Root Loop, but in any loop.

Refer to Re: What Execution System does LabVIEW use with VI server? and The Root Loop

Maximal amount of threads in a parallel for loop #

ParallelLoop.MaxNumLoopInstances=256

Save for Previous Version #

Introduced in LabVIEW 2024 and finally released in LabVIEW 2025 (so, no need to set any longer manually)

FeatureToggle.Editor.ProjectSaveVersion=True

This feature allows you to use LabVIEW 2024 Q1 to edit VIs that can be opened with older versions of the LabVIEW editor. This allows you to collaborate on a project with others who haven’t upgraded to the same version of LabVIEW that you are using. Refer to Preview Feature in LabVIEW 2024 Q1: Developing a LabVIEW Project in an Older Save Version File Format

Enabling Heap Peek and Ned #

LVdebugKeys=True

Heap Peek is a debug feature which 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.

to trigger the Heap Peek window:

  • Open your VI
  • Press CTRL+SHIFT+D+H.

to trigger the Ned Options Window

  • Press CTRL+SHIFT+D+N.

Refer to LabVIEW Wiki - Heap Peek & Lava - Heap Peek.

Additional Options for Control’s Customization #

enableSecretPopups=True

Christina talks about it a bit here on LAVA. This will add new menu Items to popup for things like centering text, or having the boolean decal grow with the button resize.

Links: 1, 2, 3.

Additional Private Property Nodes and Methods #

SuperSecretPrivateSpecialStuff=True

Enable scripting (available in VI Server) #

server.viscripting.showScriptingOperationsInEditor=True

Some additional Info: LabVIEW configuration file/Miscellaneous.

Catch internals Errors #

In case of internal errors the following keys could be helpful:

Debugging=True
LVdebugKeys=True
DPrintfLogging=True

The next time the crash happens, check one of these log files:

%temp%\LabVIEW_[bitness]_[version]_[user]_cur.txt
%temp%\LabVIEW_[bitness]_[version]_[user]_log.txt

Refer to 1 and 2.

German Locale for Run-Time #

RTLocale = "German_Germany.1252"

Create Constant/Indicator/Control Block Diagram Changes #

PopupMenus.ElevateCreation=True

With these changes, you can still tack down a broken wire… use Alt-Double Click for that now.

Refer to NI forum.