LabVIEW Wiki - User contributions [en]

LabVIEW configuration file/Miscellaneous

2009-05-27T14:58:16Z

Pbrooks100:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Configuration_File|Misc]]

LabVIEW configuration file/Miscellaneous

2009-05-27T14:48:01Z

Pbrooks100:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Configuration_File|Misc]]

LabVIEW configuration file/Miscellaneous

2009-05-27T14:46:17Z

Pbrooks100:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Configuration_File|Misc]]

LabVIEW configuration file/Miscellaneous

2009-05-27T14:45:00Z

Pbrooks100: added showNoNavDialog

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Configuration_File|Misc]]

Occurrence

2009-05-20T20:48:00Z

Pbrooks100: added reference to NI suggested use of Notifier operations

There seem to be misconceptions about how exactly occurrences work and what exactly the "ignore previous" parameter on "Wait on Occurrence" (WoO) does. The following tries to explain, in a long and winded way, how they (functionally) behave:

How Occurrences are "generated": When a VI is loaded (!) each "Generate Occurrence" function allocates exactly one unique occurrence. When the VI is running and this function is called it simply returns this one occurrence -- no matter how many times it is called (try putting one in a loop and examining its value using the probe, it will always have the same number). If you stop the VI and run it again, you will get the same value; only removing the VI from memory and loading it again will give you a "fresh" value.

How Wait On Occurrence (WoO) works: Each WoO functions "remembers" what occurence it last waited on and what time it continued (because the occurence fired or because of a timout). When a VI is loaded (!) each WoO is initialized with a non existing occurrence. When a WoO is called and "ignore previous" is FALSE there are four potential cases:

*The occurrence has *never* been set -> in this case WoO waits
*The occurrence has been set since this WoO last executed -> WoO does not wait
*The occurrence has last been set before this WoO last executed and last time this WoO was called it waited on the *same* occurrence -> WoO will wait
*The occurrence has last been set before this WoO last executed but last time this WoO was called it waited on a *different* occurrence -> WoO will *not* wait!!!!

The first three cases are pretty clear, the last one may seem a bit strange. It will only arise if you have a WoO inside a loop (or inside a *re-entrant* VI in this loop) and it waits on *different* occurrences (out of an array, for example) or if it is inside a *non re-entrant* VI and the VI is called with different occurrences. These cases do generally not happen. The reason the WoO behaves this way is due to its implementation. Each occurrence "knows" the last time it has been fired, and each WoO remembers the occurrence it was last called with and what time it fired (or timed out). When WoO is called and "ignore previous" is FALSE, it will look at its input; if the input is the same as last time, it will look at the time of the last firing and wait depending on whether the time was later than last execution; if the input is *not* the same as last time, it will simply look at the time and wait depending on whether it has *ever* been fired.

A possible (implementation) problem: It appears that occurances are "remembering" that they have been set during previous invocations of the program. One would think that generating an occurance should create a clean "non-set" occurance. This problem can be illustrated in a program that has three parallel loops with an abortable wait in each using occurances. If the program is stopped with the stop button things are fine. But if one waits until one of the random stop conditions triggers the end of the loops (generated from the other loops), the next time the program is run, the loops will execute only once and not loop at all. (The random terminate condition in the actual program is an error occuring in some piece of equipment.) Either this is a bug, or we are completely wrong on the use of occurances. Our example here is using the occurances in the "do not clear previous" mode. We would think that we will not remember ccurances from previous runs of the program since a new clear occurance should be created with the generate occurance icon. In this instance we can not use the clear previous occurances mode since we need a single occurance to stop multiple parallel loops.

The reason for the problem: The first time the occurrence is set because of an error, the loops terminate, but the "stop button" loop is still running. When you click on the stop button, the occurrence gets triggered again (unneccessarily) and the program stops. The next time the VI runs, the WoO will not wait because of this extra trigger; and since you'll trigger again in the "stop button" loop, the VI won't work until it's reloaded from disk.

A solution to the problem: Due to this behavior of occurrences, it is clear that one cannot use the "timed out" flag to determine when the occurrence fired. You will have to maintain some global information about your state, let's say in a global boolean called "FINISHED". At the beginning of the program you would initialize it to false. If you have an error, set FINISHED to true, and then trigger the occurrence. After the WoO see if FINISHED is true (make sure you don't read the global until *after* WoO finished executing), if FINISHED is false continue with the loop. In the "Stop button" loop, also set FINISHED before you trigger the occurrence.

BTW, if you don't like globals, you could use a VI with an [[Uninitialized shift register]] (LabVIEW 2 global), but the effect would be the same.

Comments: One may think that occurrences are quirky, a pain to use and that they should be avoided. One might be right! Occurrences are very low level and you often have to add functionality to them in order to use them effectively. In other words, they are not for the faint of heart. Anything implemented with occurences can be also implemented without them, but maybe not as efficently. What occurrences do is to allow you to program synchronization in a way that does not use polling, and is thus "cheaper" in processor time.

''Note: National Instruments encuorages the use of Notifier operations functions in place of the occurences for most operations.'' 

[[Category:Synchronization]]

Connector pane

2009-02-17T19:51:52Z

Pbrooks100: Added link to LabVIEW_configuration_file/Miscellaneous#defaultConPane

== Connector Panes ==

Connector panes are used in subVI's to pass parameters to and from the subVI. The connector pane is selected by right clicking on the VI icon in the upper right hand corner of your VI, then choosing the '''Show Connector''' menu item.

[[Image:Show connector selection.png|thumb|center|300px|How to view the connector pane in a VI]]

Right-click again on the VI icon and choose a pattern for you subVI's connector pane.

[[Image:Connector Pane Patterns.png|thumb|center|300px|How to select a connector pane pattern]]

It is considered good practice to choose a pattern that has more inputs/outputs than you need when writing the VI so that new inputs or outputs can be added without changing the connector pane and causing the VI's that link to your subVI to recompile.

The 4x2x2x4 pattern highlighted above is the most commonly used for NI primitives. In LabView 8 and above the connector pane is defaulted to the 4x2x2x4 pattern.

To customize the default connector pane used for new VIs, set the defaultConPane variable in your [[LabVIEW configuration file]] (see [[LabVIEW configuration file/Miscellaneous#defaultConPane|Miscellaneous>defaultConPane]]).

[[Image:ConPane.png|center|Connector pane values]]

[[Category:Calling_a_VI]]

VIT File Extension

2008-12-02T20:22:26Z

Pbrooks100:

'Vit' is the acronym and file type for LabVIEW Templates. Templates are patterns or models, used as starting points to create a new instance (copy) of that template. This new instance can either be used to perform some work in several instances (Think of communication using different channels or driving different devices.) or can be modified in order to not start on scratch but with some similar code. 
The latter use case is available with the 'File/New' command. This offers to create a new VI from one of several templates. There are templates for Data Acquisition [ [[DAQ]] ], several Frameworks and Design Patterns and some Tutorial templates.

[[category:LabVIEW file extensions]]

LabVIEW configuration file/Miscellaneous

2008-12-01T15:40:10Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ labviewconfigurationkey
| keyname = BldApp.RemovePolyVIsandTypedefs
| example =BldApp.RemovePolyVIsandTypedefs=FALSE
| datatype =b
| description =Setting this to <code>FALSE</code> stops the LabVIEW Application Builder from aggressively removing polymorphic VIs and typedefs that it thinks are not required
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 7
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.
}}
{{ labviewconfigurationkey
| keyname = coerceFromVariant
| example =coerceFromVariant=TRUE
| datatype =b
| description =Force variants to automatically coerce to any data type that they are connected to
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Tread carefully, as using this function removes coercion notification, and does not use error handling
}}
{{ labviewconfigurationkey
| keyname = cleanupVisa
| example =cleanupVisa=TRUE
| datatype =b
| description =Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = defaultConPane
| example = defaultConPane=4833
| datatype = I32
| description = Sets the default [[Connector pane]] layout for new VIs
| permitted_values =
| default = (4815)
| LV1 = 8.x
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: NI Knowledge Base
( http://digital.ni.com/public.nsf/allkb/279F064F0688C114862570900057678C )
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

Connector pane

2008-12-01T15:38:36Z

Pbrooks100:

== Connector Panes ==
Connector panes are used in subVI's to pass parameters to and from the subVI. The connector pane is selected by right clicking on the VI icon in the upper right hand corner of your VI, then choosing the '''Show Connector''' menu item.

[[Image:Show_connector_selection.png‎|thumb|300px|center|How to view the connector pane in a VI]]

Right-click again on the VI icon and choose a pattern for you subVI's connector pane.

[[Image:Connector_Pane_Patterns.png|thumb|300px|center|How to select a connector pane pattern]]

It is considered good practice to choose a pattern that has more inputs/outputs than you need when writing the VI so that new inputs or outputs can be added without changing the connector pane and causing the VI's that link to your subVI to recompile.

The 4x2x2x4 pattern highlighted above is the most commonly used for NI primitives. In LabView 8 and above the connector pane is defaulted to the 4x2x2x4 pattern.

To customize the default connector pane used for new VIs, set the defaultConPane variable in your [[LabVIEW configuration file]] (see Miscellaneous>defaultConPane).

[[Image:ConPane.png|center|Connector pane values]]

[[category:calling a VI]]

Connector pane

2008-12-01T15:36:56Z

Pbrooks100:

== Connector Panes ==
Connector panes are used in subVI's to pass parameters to and from the subVI. The connector pane is selected by right clicking on the VI icon in the upper right hand corner of your VI, then choosing the '''Show Connector''' menu item.

[[Image:Show_connector_selection.png‎|thumb|300px|center|How to view the connector pane in a VI]]

Right-click again on the VI icon and choose a pattern for you subVI's connector pane.

[[Image:Connector_Pane_Patterns.png|thumb|300px|center|How to select a connector pane pattern]]

It is considered good practice to choose a pattern that has more inputs/outputs than you need when writing the VI so that new inputs or outputs can be added without changing the connector pane and causing the VI's that link to your subVI to recompile.

The 4x2x2x4 pattern highlighted above is the most commonly used for NI primitives. In LabView 8 and above the connector pane is defaulted to the 4x2x2x4 pattern.

To customize the default connector pane used for new VIs, set the defaultConPane variable in your [[LabVIEW configuration file]].

[[Image:ConPane.png|center|Connector pane values]]

[[category:calling a VI]]

Connector pane

2008-12-01T15:30:31Z

Pbrooks100: Added image - Connector pane choices with defaultConPane values overlay

== Connector Panes ==
Connector panes are used in subVI's to pass parameters to and from the subVI. The connector pane is selected by right clicking on the VI icon in the upper right hand corner of your VI, then choosing the '''Show Connector''' menu item.

[[Image:Show_connector_selection.png‎|thumb|300px|center|How to view the connector pane in a VI]]

Right-click again on the VI icon and choose a pattern for you subVI's connector pane.

[[Image:Connector_Pane_Patterns.png|thumb|300px|center|How to select a connector pane pattern]]

It is considered good practice to choose a pattern that has more inputs/outputs than you need when writing the VI so that new inputs or outputs can be added without changing the connector pane and causing the VI's that link to your subVI to recompile.

The 4x2x2x4 pattern highlighted above is the most commonly used for NI primitives. In LabView 8 and above the connector pane is defaulted to the 4x2x2x4 pattern.

To customize the default connector pane used for new VIs, set the defaultConPane variable in your LabVIEW.ini file.

[[Image:ConPane.png|center|Connector pane values]]

[[category:calling a VI]]

File:ConPane.png

2008-12-01T15:22:26Z

Pbrooks100: Connector Pane options with conPane values superimposed

Connector Pane options with conPane values superimposed

Symbolic path

2008-11-26T11:17:37Z

Pbrooks100: added <osdatadir> to symbolic paths; available back to LV 7.0

When files are located beneath certain special folders, callers that link to these files will link to them using a ''symbolic path'', rather than an absolute or relative path. The ''symbolic path'' will be relative to the special folder. The following table lists these special folders and their ''symbolic path'':

{| class="wikitable"
|-
! symbolic path
! description
! actual path
|-
| <userlib>
| User Libraries
| <LabVIEW>\user.lib
|-
| <vilib>
| NI Libraries and Addons
| <LabVIEW>\vi.lib
|-
| <instrlib>
| Instrument Drivers
| <LabVIEW>\instr.lib
|-
| <help>
| Help Files
| <LabVIEW>\help
|-
| <osdatadir>
| Default file directory of the operating system
| (OS Dependent)
|-
| <menu>
| Palette Menus
| <LabVIEW>\menus
|}

Note that some of these can have the actual path changed by changing the settings in '''Tools>>Options'''. The whole point of the symbolic path is to indicate "load from whatever location this path is currently defined to be."

For example, if you have a VI located in the following location:

<LabVIEW>\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi

Callers will link to this VI using the following ''symbolic path'':

<userlib>\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi

''symbolic path'' are not generally encountered. They are used mostly under the hood of LabVIEW, for example, when using the Application '''Linker:Read Info From File''' and '''Linker:Write Info To File''' methods.

== Resolving Symbolic Paths Programmatically==

You can call the private '''Resolve Symbolic Path''' method to convert a Symbolic Path to an absolute path, as shown in the screenshot, below.

[[Image:ResolveSymbolicPath.png]]

You can download a VI with this private method, here: [http://forums.lavag.org/post-a10538-ResolveSymbolicPath.vi ResolveSymbolicPath.vi]

== Auto update of symbolic paths ==
If you have a VI linked to another VI inside a symbolic path LabVIEW will automatically store the path symbolically. Here's the following use case:

Suppose you want to build a LabVIEW tool that resides under the Tools menu but is also accessible via the user.lib palette. What you can do is create a set-up upon built like this:

*[Built]
**[Tools]
***Menu VI
**[user.lib]
***Actual VI

When you copy the contents of ''Built'' to the LabVIEW folder the ''Menu VI'' will have a relative path like ''..\user.lib\Actual VI'' when you do a resave of the ''Menu VI'' the path will be changed to an absolute path ''<userlib>\Actual VI''. Now you can move the ''Menu VI'' around without breaking it.

== When Using Modules (FPGA, RT, etc) ==
A symbolic path may resolve to different actual files on disk depending upon which target the VI is loaded into. So a VI that is written to use <vilib>\a.vi may use <labview>\vi.lib\a.vi when loaded for the desktop target, but may use <labview>\vi.lib\fpga\a.vi when loaded for the FPGA target.

== External Links ==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/using_symbolic_paths/ LabVIEW Help: Using Symbolic Paths]

[[category:development environment]]
[[category:File IO]]

LabVIEW configuration file/Miscellaneous

2008-09-08T12:56:57Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ labviewconfigurationkey
| keyname = BldApp.RemovePolyVIsandTypedefs
| example =BldApp.RemovePolyVIsandTypedefs=FALSE
| datatype =b
| description =Setting this to <code>FALSE</code> stops the LabVIEW Application Builder from aggressively removing polymorphic VIs and typedefs that it thinks are not required
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 7
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.
}}
{{ labviewconfigurationkey
| keyname = coerceFromVariant
| example =coerceFromVariant=TRUE
| datatype =b
| description =Force variants to automatically coerce to any data type that they are connected to
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Tread carefully, as using this function removes coercion notification, and does not use error handling
}}
{{ labviewconfigurationkey
| keyname = cleanupVisa
| example =cleanupVisa=TRUE
| datatype =b
| description =Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = defaultConPane
| example = defaultConPane=4833
| datatype = I32
| description = Sets the default connector pane layout for new VIs
| permitted_values =
| default = (4815)
| LV1 = 8.x
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: NI Knowledge Base
( http://digital.ni.com/public.nsf/allkb/279F064F0688C114862570900057678C )
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-09-08T12:55:13Z

Pbrooks100: changed notes to point to the NI Knowledge Base entry

This is a list of Miscellaneous LabVIEW ini File settings.

{{ labviewconfigurationkey
| keyname = BldApp.RemovePolyVIsandTypedefs
| example =BldApp.RemovePolyVIsandTypedefs=FALSE
| datatype =b
| description =Setting this to <code>FALSE</code> stops the LabVIEW Application Builder from aggressively removing polymorphic VIs and typedefs that it thinks are not required
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 7
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.
}}
{{ labviewconfigurationkey
| keyname = coerceFromVariant
| example =coerceFromVariant=TRUE
| datatype =b
| description =Force variants to automatically coerce to any data type that they are connected to
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =Tread carefully, as using this function removes coercion notification, and does not use error handling
}}
{{ labviewconfigurationkey
| keyname = cleanupVisa
| example =cleanupVisa=TRUE
| datatype =b
| description =Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = defaultConPane
| example = defaultConPane=4833
| datatype = I32
| description = Sets the default connector pane layout for new VIs
| permitted_values =
| default = (4815)
| LV1 = 8.x
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: NI Knowledge Base
(http://digital.ni.com/public.nsf/allkb/279F064F0688C114862570900057678C)
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-08-31T18:37:57Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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: Darren's Weekly Nugget 03/06/2006
(http://forums.ni.com/ni/board/message?board.id=170&message.id=171692&query.id=2343#M171692)
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-08-29T11:38:18Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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 = U32
| description = Sets the default connector pane layout for new VIs
| permitted_values =
| default = (7.1 = -1; 8.x = 4815)
| LV1 = 7.1
| LV2 = 8.x
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: Darren's Weekly Nugget 03/06/2006
(http://forums.ni.com/ni/board/message?board.id=170&message.id=171692&query.id=2343#M171692)
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-08-29T11:17:29Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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 = U32
| description = Sets the default connector pane layout for new VIs
| permitted_values =
| default = (7.1 = -1; 8.x = 4815)
| LV1 = 7.1
| LV2 = 8.x
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: Darren's Weekly Nugget 03/06/2006 (http://forums.ni.com/ni/board/message?board.id=170&message.id=171692&query.id=2343#M171692)
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype = i
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-08-29T11:10:23Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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 = U32
| description = Sets the default connector pane layout for new VIs
| permitted_values =
| default = -1
| LV1 = 8.x
| LV2 = 7.x
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: Darren's Weekly Nugget 03/06/2006 (http://forums.ni.com/ni/board/message?board.id=170&message.id=171692&query.id=2343#M171692)
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype =b
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-08-29T11:09:54Z

Pbrooks100: Added defaultConPane=[number]

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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=[number]
| example = defaultConPane=4833
| datatype = U32
| description = Sets the default connector pane layout for new VIs
| permitted_values =
| default = -1
| LV1 = 8.x
| LV2 = 7.x
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 =
| notes = Source: Darren's Weekly Nugget 03/06/2006 (http://forums.ni.com/ni/board/message?board.id=170&message.id=171692&query.id=2343#M171692)
}}
{{ labviewconfigurationkey
| keyname = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype =b
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

User:Pbrooks100

2008-08-06T13:08:10Z

Pbrooks100:

User:Pbrooks100

2008-08-06T13:07:42Z

Pbrooks100:

LabVIEW configuration file/Unknown

2008-07-17T12:59:20Z

Pbrooks100: FancyFPTerms removed from this list - now documented in http://wiki.lavag.org/LabVIEW_configuration_file/Block_Diagram#FancyFPTerms

This is a placeholder for a page that would contain LabVIEW configuration keys that cannot be explained or described because we don't have enough information about what they do.

INI key list from LabVIEW 8.50 (many known ones exist in here, this needs to be sorted and categorized):
<ul><li>"INI_KEY (variable type) default_value"</li></ul>
<ul>
<li>/027usePaletteMenuOnMenuBar (Bool) 1
</li><li>9serviceLocatorLocalOnly (Bool) 0
</li><li>abortMin (I32 ) 1F4h
</li><li>activeX.freeThreaded[0Dh] (Bool) 1
</li><li>ActiveXContainerDefaultInDesignMode (Bool) 0
</li><li>ActiveXMoreContainerOptions (Bool) 0
</li><li>ActiveXPropertyBrowser.AutoHide (Bool) 0
</li><li>addBulletCastInWDTMutation (Bool) 1
</li><li>addProjectOptionsToFileNewDlg (Bool) 0
</li><li>AdviceEnabled (Bool) 0
</li><li>allowDragDropFromFileDlg (Bool) 0
</li><li>AllowManualLoadUnloadCvtFile (Bool) 0
</li><li>allowMultipleInstances (Bool)
</li><li>allowNoLockingForEvents (Bool) 1
</li><li>allowOpenFPOfInstanceVIs (Bool) 0
</li><li>allowPreallocsInDll (Bool) 0
</li><li>AllowRunTimeFontChangeOnPaste (Bool) 0
</li><li>allowSetUnicodeStyle (Bool) 0
</li><li>AlphabetizeVIServerClassMenu (Bool) 1
</li><li>AppDomainSetup_CachePath (Path)
</li><li>AppDomainSetup_DisallowBindingRedirects (Bool) 0
</li><li>AppDomainSetup_DisallowCodeDownload (Bool) 0
</li><li>AppDomainSetup_DisallowPublisherPolicy (Bool) 0
</li><li>AppDomainSetup_DynamicBase (Path)
</li><li>AppDomainSetup_LicenseFile (Path)
</li><li>AppDomainSetup_ShadowCopyFiles (Bool) 1
</li><li>appFont (Font) 0
</li><li>AssistantsUseStrictTypes
</li><li>AssistantsUseStrictTypes (Bool) 0
</li><li>asynchWiresEnabled (I32 ) 0
</li><li>autoDeployOnVIRun (Bool) 1
</li><li>autoerr (Bool) 0
</li><li>autoInsertFeedbackNode (Bool) 1
</li><li>autoPreallocate (Bool) 0
</li><li>autoProbe (Bool) 1
</li><li>autoRouteWires (Bool) 1
</li><li>AutoSaveEnabled (Bool) 1
</li><li>AutoSaveTimeoutMinutes (I32 ) 5
</li><li>AutoSaveTimerEnabled (Bool) 1
</li><li>autoTool (Bool) 1
</li><li>autoTool.allowLabelOnBD (Bool) 0
</li><li>autoTool.allowLabelOnFP (Bool) 0
</li><li>autoTool.changeBoolValsOnBD (Bool) 1
</li><li>autoTool.changeBoolValsOnFP (Bool) 0
</li><li>autoTool.changeNumValsOnBD (Bool) 1
</li><li>autoTool.changeNumValsOnFP (Bool) 1
</li><li>autoTool.doubleClickLabels (Bool) 1
</li><li>autoTool.wireWires (Bool) 0
</li><li>autoToolOn (Bool) 1
</li><li>autoWireMax (I32 ) 20h
</li><li>autoWireMin (I32 ) 04h
</li><li>BDFont (Font) 0
</li><li>BigSavingsFormat (PStr)
</li><li>BitmapFontSmallerMultiplier (I32 ) 1.3
</li><li>blinkBG (Colr) 0FF0000h
</li><li>blinkFG (Colr) 0FFFF00h
</li><li>blinkSpeed (I32 ) 3E8h
</li><li>BuildPDAPrc (Bool) 1
</li><li>CallistoAutoReload (Bool) 1
</li><li>CallistoSimpleWires (Bool) 0
</li><li>callLibNodeMayHaveLVClassParams (Bool) 0
</li><li>CBoxCommentColor (Colr) 7F5Fh
</li><li>CBoxConstantColor (Colr) 0
</li><li>CBoxDataTypeColor (Colr) 09Dh
</li><li>CBoxDefaultColor (Colr) 0
</li><li>CBoxExternalEditorPath (Path)
</li><li>CBoxKeywordColor (Colr) 55003Fh
</li><li>CBoxModifierColor (Colr) 045h
</li><li>CBoxPreprocessorColor (Colr) 055h
</li><li>CBoxStringColor (Colr) 0FFh
</li><li>CBoxTabSize (I32 ) 8
</li><li>CCodeGenDir (Path) 0
</li><li>CDIntervalTicks (I32 ) 7
</li><li>CGenBuildApp (Bool) 1
</li><li>CGenDownloadApp (Bool) 1
</li><li>CGenLaunchAction (I32 ) 0
</li><li>checkActiveXLibs (Bool) 0
</li><li>checkAvailDiskSpace (Bool) 1
</li><li>checkFontSize (Bool) 0
</li><li>CheckHighWaterMarks (Bool)
</li><li>checkQElements (Bool) 0
</li><li>ClassBrowserEnabled (Bool) 1
</li><li>cleanupVisa (Bool) 0
</li><li>closeConfVIOnBDClose (Bool) 1
</li><li>coerceFromVariant (Bool) 0
</li><li>coercionDotmColor (Colr) 0xFF0000
</li><li>colorHistoryItemA (Colr) 3452540h
</li><li>colorHistoryItemB (Colr) 3452540h
</li><li>colorHistoryItemC (Colr) 3452540h
</li><li>colorHistoryItemD (Colr) 3452540h
</li><li>colorHistoryItemE (Colr) 3452540h
</li><li>colorHistoryItemF (Colr) 3452540h
</li><li>colorHistoryItemG (Colr) 3452540h
</li><li>colorHistoryItemH (Colr) 3452540h
</li><li>colorHistoryItemI (Colr) 3452540h
</li><li>colorHistoryItemJ (Colr) 3452540h
</li><li>colorHistoryItemK (Colr) 3452540h
</li><li>colorPrinting (Bool) 1
</li><li>colorUserItem (Colr) 35A368Ch
</li><li>compileOptimizeFlags (I32 ) 5
</li><li>confDiagEnabled (Bool) 0
</li><li>ContextHelpLoc (Rect)
</li><li>controlPropertyPages (Bool) 1
</li><li>convert4xData (Bool) 1
</li><li>copyDeleteFPDCOFromFPTerm (Bool) 1
</li><li>createDefaultProject (Bool) 0
</li><li>createLogFile (Bool)
</li><li>ctlEditNoQuestions (Bool) 0
</li><li>cursor.background (Colr) 0FFFFFFh
</li><li>cursor.foreground (Colr) 0
</li><li>CustomShortcuts (ECPS) 1
</li><li>DAbortDialog (Bool)
</li><li>dateDayFirst (Bool) 0
</li><li>dateSeparator (I32 ) 0
</li><li>DbgSkipAssertIdentsAndVIsMatch (Bool) 1
</li><li>DebugDlgSkipList (CPSt)
</li><li>debugging (Bool)
</li><li>debugkeys (Bool)
</li><li>DebugLogSkipList (CPSt)
</li><li>DebugSimScripting (Bool) 0
</li><li>debugVHDL (Bool) 0
</li><li>defaultControlFormat (PStr)
</li><li>defaultControlStyle (I32 ) 0
</li><li>DefaultDataFileLocation (Path)
</li><li>defaultdir (Path) 0
</li><li>defaultErrorHandlingForNewVIs (Bool) 1
</li><li>defaultIndicatorFormat (PStr)
</li><li>DefaultLabelLockBD (Bool) 0
</li><li>DefaultLabelLockFP (Bool) 0
</li><li>DefaultLabelPositionBD (I32 ) 0
</li><li>DefaultLabelPositionFP (I32 ) 0
</li><li>DefaultPingDelay (I32 ) 2710h
</li><li>DefaultPingTimeout (I32 ) 2710h
</li><li>diagram.background (Colr) 0xFFFFFF
</li><li>diagram.primColor (Colr) 0xFFFFCC
</li><li>DialogBoolsOnlyUseWindowsKeys (Bool) 1
</li><li>dialogFont (Font) 0
</li><li>diff.circles (Bool) 1
</li><li>diff.showMatches (Bool) 0
</li><li>diff.tileVert (Bool) 1Ah
</li><li>disableBatchAdd (Bool) 0
</li><li>disableCrossLinkWarningDlgs (I32 ) 3Fh
</li><li>disableMenuEffects (Bool) 0
</li><li>DisableTargetSyntaxChecking (Bool) 0
</li><li>dithering (Bool) 0
</li><li>DNSLookupEnabled (Bool) 1
</li><li>dontGiveInstanceVIsTitles (Bool) 0
</li><li>DontShowProjectAddDialog (Bool) 0
</li><li>DontShowProjectAddDialog2 (Bool) 0
</li><li>DontShowProjectAddDialogDoNotAdd (Bool) 0
</li><li>DontShowProjectRemoveDialog (Bool) 0
</li><li>DontShowProjectRemoveDialogNonFile (Bool) 0
</li><li>DontUseAltTab (Bool) 0
</li><li>doObjPathChecking (Bool) 1
</li><li>doubleClickToEditControl (Bool) 0
</li><li>DPrintfLogging (Bool) 0
</li><li>DPrintfToFile (Bool)
</li><li>drawFPTermArrow (Bool) 1
</li><li>DropSubsystemsAsXNode (Bool) 1
</li><li>dropThroughClicks (Bool) 1
</li><li>DSWriteTimeout (I32 ) ?
</li><li>dumpLoadLog (Bool) 0
</li><li>DWarnDialog (Bool) 0
</li><li>DWarnDialogMultiples (Bool) 0
</li><li>DWarnLogging (Bool) 1
</li><li>editInMultipleContexts (Bool) 1
</li><li>editor.liveUpdates (Bool) 0
</li><li>editor.smartWiring (Bool) 0
</li><li>editRecentPaths (PLst) 0
</li><li>editRTMenusFromRsrc (Bool) 0
</li><li>EnableAutomaticErrorHandling (Bool) 1
</li><li>EnableAutomaticErrorHandlingRT (Bool) 0
</li><li>enableAutoScales (Bool) 1
</li><li>enableAutoWire (Bool) 1
</li><li>enableCustomInterface (Bool) 1
</li><li>enableGroupLock (Bool) 1
</li><li>EnableIGL (Bool) 0
</li><li>EnableIGLStressTest (Bool) 0
</li><li>enableMultiScales (Bool) 1
</li><li>EnableMultiThreadedLoad (Bool) 0
</li><li>enableRelativeSharedVariableNodes (Bool) 1
</li><li>enableShellExtension (Bool) 1
</li><li>EnableStrictTypedefConstantConfiguration (Bool) 0
</li><li>EnableTimeDataNodeHiddenElements (Bool) 0
</li><li>EnableTimedLoops (Bool) 1
</li><li>ESys.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.DAQ.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.DAQ.High (I32 ) 144E07Bh
</li><li>ESys.DAQ.Normal (I32 ) 144E07Bh
</li><li>ESys.DAQ.TCritical (I32 ) 144E07Bh
</li><li>ESys.DAQ.VHigh (I32 ) 144E07Bh
</li><li>ESys.High (I32 ) 144E07Bh
</li><li>ESys.instrument.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.instrument.High (I32 ) 144E07Bh
</li><li>ESys.instrument.Normal (I32 ) 144E07Bh
</li><li>ESys.instrument.TCritical (I32 ) 144E07Bh
</li><li>ESys.instrument.VHigh (I32 ) 144E07Bh
</li><li>ESys.Normal (I32 ) 144E07Bh
</li><li>ESys.other1.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.other1.High (I32 ) 144E07Bh
</li><li>ESys.other1.Normal (I32 ) 144E07Bh
</li><li>ESys.other1.TCritical (I32 ) 144E07Bh
</li><li>ESys.other1.VHigh (I32 ) 144E07Bh
</li><li>ESys.other2.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.other2.High (I32 ) 144E07Bh
</li><li>ESys.other2.Normal (I32 ) 144E07Bh
</li><li>ESys.other2.TCritical (I32 ) 144E07Bh
</li><li>ESys.other2.VHigh (I32 ) 144E07Bh
</li><li>ESys.StdNParallel (I32 ) 4
</li><li>ESys.TCritical (I32 ) 144E07Bh
</li><li>ESys.VHigh (I32 ) 144E07Bh
</li><li>EventLogging.EnableVITracing (Bool) 0
</li><li>examplesDir (Path) 0
</li><li>ExecEngineSelectPrompt (Bool) 0
</li><li>execPalette.background (Colr) 1000030h
</li><li>execPalette.foreground (Colr) 0
</li><li>execRecentPaths (PLst) 0
</li><li>execThreadStackOffsetIncr (I32 ) 40h
</li><li>exposedTypeDefsEnabled (Bool) 1
</li><li>expressLeaveWizardsOpenAfterLaunch (Bool) 0
</li><li>ExternalNodeDebugging (Bool) 0
</li><li>ExternalNodesEnabled (Bool) 0
</li><li>extFuncCatching (I32 ) 1
</li><li>extFuncExtendedOptionsEnabled (Bool) 0?
</li><li>extFuncGenNoWrapperEnabled (Bool) 0
</li><li>fadeEphemeralWires (Bool) 0
</li><li>fastPreSCFlatGeneration (Bool) 0
</li><li>FilterExec (Bool) 1
</li><li>find.findTextFlags (I32 ) 6C6F6F42h "Bool"
</li><li>find.nodeRsrcID (I32 ) 41Ah
</li><li>find.searchStr (PStr) 0
</li><li>find.viListFlags (I32 ) 0
</li><li>findIPPathEnabled (Bool) 1
</li><li>FindSpaceCreateZone (I32 ) 96h
</li><li>FindSpaceOnCreate (Bool) 1
</li><li>firstDiffMonitor (I32 ) 6C6F6F42h "Bool"
</li><li>FlatLibChain (Bool) 1
</li><li>flushDrawing (Bool) 1
</li><li>formulaBoxPrecision (PStr) ????
</li><li>FPDSConnectTimeout (I32 ) 61A8h
</li><li>FPFont (Font) 0
</li><li>FPUpdateRate (I32 ) 0Ah
</li><li>funkyErrClustWire (Bool) 1
</li><li>FXPDefaultIntWordLength (I32 ) 10h
</li><li>FXPDefaultSigned (Bool) 1
</li><li>FXPDefaultWordLength (I32 ) 20h
</li><li>gCachedArc.extreme (Bool) 1
</li><li>genDualInterface (Bool) 1
</li><li>graphReadsAttributes (Bool) 1
</li><li>grayOutMethod (PStr)
</li><li>growSubVI.defaultStyle (I32 ) 29h
</li><li>growSubVI.enabled (Bool) 0
</li><li>HardWaitTimeCritical (Bool)
</li><li>HardWaitVeryHigh (Bool)
</li><li>help.showconnums (Bool) 0
</li><li>HelpServerEnabled (Bool) 0
</li><li>helpServerEnabled (Bool) 1
</li><li>hideEmptySubPalettes (Bool) 0
</li><li>hideRootWindow (Bool) 0
</li><li>hierarchy.stateFlags (I32 ) 47h
</li><li>HierarchyWindow.ProjectView (Bool) 1
</li><li>HierarchyWindow.ShowPrivateApp (Bool) 0
</li><li>HierarchyWindow.ZeroUserProjectNoProjectView (Bool) 1
</li><li>HiliteExecutionPride (Bool) 0
</li><li>HiliteExecutionWhosePride (Path) 0
</li><li>history.alwaysRecordChange (Bool) 0
</li><li>history.generateComments (Bool) 0
</li><li>history.promptAtClose (Bool) 0
</li><li>history.promptAtSave (Bool) 0
</li><li>history.whereToGetName (PStr) 0
</li><li>honorOffScreenSettings (Bool) 1
</li><li>hotMenus (Bool) 1
</li><li>hour24 (Bool) 0
</li><li>i386_AlignedLabels (Bool)
</li><li>i386_CacheAlign (I32 ) 40h
</li><li>i386_CacheAlign (I32 ) 40h
</li><li>IconFont (Font) 0xFFFFFF ???
</li><li>ignoreHelpAndProjDirs (Bool) 0
</li><li>imagesCompressedInMem (Bool) 0
</li><li>independentImageDepth (I32 ) 0
</li><li>inlineSubVIEnabled (Bool) 0
</li><li>inplaceRefOutputsEnabled (I32 ) 1
</li><li>int64Enabled (Bool) 1
</li><li>InternetToolkitInstalled (Bool) 0
</li><li>ipConstantsEnabled (Bool) 0
</li><li>IsFirstLaunch (Bool) 1
</li><li>kctCPDADirPath (Path) 0
</li><li>keepDotNetDomainAlive (Bool) 0
</li><li>keepIntensityBitmap (Bool) 0
</li><li>keyboardAccelerateSave (Bool) 0
</li><li>LastErrorListSize (Rect) 0
</li><li>LaunchConfigurationPageAfterDropExpressBlock (Bool) 1
</li><li>launchNewWorkspaceOnStart (Bool) 0
</li><li>LaunchScreenTextBGColor (Colr) 0FFBB00h
</li><li>LaunchTimeBenchmarking (Bool) 0
</li><li>leftClickPopupPalette (Bool) 0
</li><li>libdir (Path) 0
</li><li>ListboxSelectionStyle (PStr) 0???
</li><li>ListboxSelectionVersion (PStr) 0???
</li><li>loadAlwaysSearches (fMv03) 1
</li><li>LoadGWSAtStart (Bool) 0
</li><li>LocalHost (Path) 0
</li><li>LogFileSaved (Bool) 0
</li><li>LVClassOutputsDynamicByDefault (Bool) 1
</li><li>LVdebugKeys (Bool) 0
</li><li>lvPictImagesSavedCompressed (Bool) 1
</li><li>LVTargets (Path) 0
</li><li>marginB (I32 ) 0
</li><li>marginL (I32 ) 0
</li><li>marginR (I32 ) 0
</li><li>marginT (I32 ) 0
</li><li>marginUnitInch (Bool) 1
</li><li>mathScriptPath (PLst)
</li><li>MaxDPrintfsLogged (I32 )
</li><li>MaxDWarnsLog (I32 )
</li><li>maxUndoSteps (I32 ) 8
</li><li>maxVISizeForMemoryUncompress (I32 ) 400000h
</li><li>memoryChecking (Bool)
</li><li>menu.1 (Path)
</li><li>menu.background (Colr) 100002Eh
</li><li>menu.foreground (Colr) 100002Dh
</li><li>menubar.background (Colr) 1000030h
</li><li>menubar.foreground (Colr) 100002Fh
</li><li>MenuMRUItems (LStr) 0
</li><li>mergeAdjVirtualAllocs (Bool)
</li><li>MinMNGFrameDelay (I32 ) 0
</li><li>moveDefaultContextVIsToProjContext (Bool) 0
</li><li>MRUFolders (Bool) 0
</li><li>mutateToPeriodDecimalPoint (I32 ) 0
</li><li>netconn (Bool) 1
</li><li>NISecurityTimeout (I32 ) 2710h
</li><li>noBoxAroundName (Bool) 1
</li><li>nodeBreakPointMenuItem (Bool) 0
</li><li>nonDirectionalSignals (Bool) 0
</li><li>NoSavePromptForReadonlyLocked (Bool) 0
</li><li>NoTypeBanner (Bool)
</li><li>numStatusItemsToLog (I32 ) 0
</li><li>offscreenUpdates (Bool) 1
</li><li>OldStyleSave (Bool) 0
</li><li>ole.AuthnLevel (I32 )
</li><li>ole.ImpLevel (I32 )
</li><li>OleVariantList (Bool) 0
</li><li>openInRun (Bool) 0
</li><li>overanxiousMemoryDeallocation (Bool) 0
</li><li>overrideLoadWarningDialog (Bool) 0
</li><li>paintPixmap (Bool) 0
</li><li>paletteAsyncLoad (Bool) 1
</li><li>PaletteHidddenControlCategories_LocalHost (LStr)
</li><li>PaletteHidddenFunctionlCategories_LocalHost (LStr)
</li><li>paletteLazyLoad (Bool) 0
</li><li>PaletteNavBarStyle (PStr)
</li><li>paletteStyle (PStr)
</li><li>panel.background (Colr) 0B3B3B3h
</li><li>PathManagerImplementation (P255)
</li><li>pinPlotLegendLeft (Bool) 0
</li><li>playAnimatedImages (Bool) 1
</li><li>PlotHitThreshold (I32 ) 2
</li><li>PolySelectorEnabledAtDrop (Bool) 1
</li><li>populateLibs (Bool) 0
</li><li>postScriptLevel2 (Bool) 1
</li><li>postScriptPrinting (Bool) 0
</li><li>preAllocateEnabled (Bool) 1
</li><li>preAllocateStringsUIEnabled (Bool) 0
</li><li>preAllocateUIEnabled (Bool) 0
</li><li>preloadSCScriptingVIs (Bool) 0
</li><li>preloadSimScriptingVIs (Bool) 1
</li><li>prettyExecHilite (Bool) 1
</li><li>printCGenFileAndLineNumbers (Bool) 0
</li><li>printerDithering (Bool) 0
</li><li>printUsingBitmap (Bool) 0
</li><li>ProbeDefaultCache (PLst)
</li><li>ProbeIniCache_8.5 (PLst)
</li><li>project.EditorMode (PStr) 0
</li><li>project.maximizeFrame (Bool) 1
</li><li>project.subduedMDIFrame (Bool) 1
</li><li>project.windowsStayOutAfterRun (Bool) 0
</li><li>projectDebugPumpOSMsgs (Bool) 0
</li><li>projectInternalOptions (I32 ) 0C0h
</li><li>projectProviderSearchPaths
</li><li>projectProviderSearchPaths (PLst)
</li><li>promoteDWarnInternals (Bool)
</li><li>promptToSaveNewProjects (Bool) 0
</li><li>PSPFPLEDVisibleDefault (Bool) 1
</li><li>PumpOSMsgsinCallback (Bool) 0
</li><li>PWNT_AlignedLabels (Bool)
</li><li>PWNT_CacheAlign (I32 )
</li><li>quickMenuProperties (Bool) 0
</li><li>readOnlyLock (Bool) 0
</li><li>RecentFiles.maxNum (I32 ) 0Ah
</li><li>RecentFiles.pathList (PLst) 0
</li><li>RecentFiles.projectPathList (PLst) 0
</li><li>RecentFiles.showFullPath (Bool) 0
</li><li>RecentTemplates.maxNum (I32 ) 0Ah
</li><li>RecentTemplates.pathList (PLst) 0
</li><li>RecompileOnLibChange
</li><li>recursiveTypesEnabled (Bool) 0
</li><li>RegisterExtensions (Bool) 1
</li><li>RelaxQualifiedNameMatching (Bool) 0
</li><li>RemotePanel.InactiveCloseTimeout (I32 ) 0
</li><li>RemotePanel.InactivePingTimeout (I32 ) 0
</li><li>RemotePanel.InactiveTimeoutEnabled (Bool) 0
</li><li>RemotePanel.MaxMsgBacklog (I32 ) 0
</li><li>RemotePanel.MaxMsgBacklogInSecs (I32 ) 0
</li><li>RemotePanel.NetloadLogInterval (I32 ) 0
</li><li>RemotePanel.NetloadLogInterval (I32 ) 0
</li><li>RemotePanel.NetloadLogNumOfSamples (I32 ) 0
</li><li>RemotePanel.NetloadLogNumOfSamples (I32 ) 0
</li><li>RemotePanel.ServerTimeoutInSecs (I32 ) 0
</li><li>RemotePanel.ServerTimeoutInSecs (I32 ) 0
</li><li>RemotePanel.VIControlTimeLimit (I32 ) 0
</li><li>ReportMovingVIs (Bool) 1
</li><li>reqdTermsByDefault (Bool) 0
</li><li>requireAutoTool (Bool) 1
</li><li>resettingDlgDelay (I32 ) 44Ch
</li><li>returnKeyAction (Bool) 0
</li><li>RTTarget.ApplicationPath (Path) 0
</li><li>RTTarget.EnableFileSharing (Bool) 0
</li><li>RTTarget.IPAccess (CPSt) 1: ""
</li><li>RTTarget.LaunchAppAtBoot (Bool) 0
</li><li>RTTarget.VIPath (Path) 0
</li><li>runSCSemanticCheck (Bool) 1
</li><li>rviDir (Path) 0
</li><li>SaveBackIntoOriginalFile (Bool) 1
</li><li>SaveChanges_ApplyToAll (Bool) 0
</li><li>SaveChanges_ExpandedAffectedFileList (Bool) 1
</li><li>saveFloaterLocations (Bool) 1
</li><li>ScaledToFitVisible (Bool) 0
</li><li>SCCConfigData (LStr)
</li><li>SCCDisplayOnlySelected (Bool) 1
</li><li>SCCDisplayWarningIfCheckedOut (Bool) 1
</li><li>SCCIncludeInstrLibInGetDependents (Bool) 1
</li><li>SCCIncludeVILibInGetDependents (Bool) 1
</li><li>SCCLocalPath (Path)
</li><li>SCCProjectName (LStr) 0
</li><li>SCCPromptToAddToAddSubVIs (Bool) 1
</li><li>SCCPromptToAddToProject (Bool) 1
</li><li>SCCPromptToCheckOut (Bool) 1
</li><li>SCCProviderLocation (LStr)
</li><li>SCCProviderName (LStr)
</li><li>SCCSelectCallersWhenCheckedOut (Bool) 1
</li><li>SCCSelectHierarchyWhenAdd (Bool) 1
</li><li>SCCUseDialogBox (Bool) 0
</li><li>Scripting_LabVIEWInternalTag (Bool) 0
</li><li>scriptNodeWait (I32 ) 0
</li><li>scrollbar.background (Colr) 1000032h
</li><li>scrollbar.foreground (Colr) 1000031h
</li><li>scrollGraphCursors (Bool) 1
</li><li>scrollingStripCharts (Bool) 0
</li><li>secondDiffMonitor (I32 ) 1
</li><li>security.keyboardACL (LStr) 0
</li><li>security.loginMode (Bool) 0
</li><li>security.SVEDomain (LStr) 0
</li><li>security.SVELoginMode (Bool) 0
</li><li>security.SVEUsername (LStr) 0
</li><li>server.tcp.port (I32 ) 0
</li><li>serviceLocatorEnabled (Bool) 1
</li><li>serviceLocatorTimeout (I32 ) 1F4h
</li><li>showAllPalettes (Bool) 0
</li><li>ShowAllVIsInErrorWindow (Bool) 0
</li><li>showBDConstName (Bool) 0
</li><li>showConfVIFrontPanel (Bool) 0
</li><li>showDatatypeOnFancyTerms (Bool) 1
</li><li>showDefaultErrorHandlingDebugBtn (Bool) 0
</li><li>ShowDSCFeaturePacks (Bool) 0
</li><li>showEmptyHistoryEntries (Bool) 0
</li><li>showExePathInWindowTitle (Bool) 0
</li><li>showFullPathOfInstanceVIs (Bool) 0
</li><li>showGridTipStrips (Bool) 1
</li><li>ShowGWS (Bool) 0
</li><li>ShowHiddenLibraryItems (Bool) 0
</li><li>showHiddenUserDefinedRefnumClasses (Bool) 0
</li><li>showNoNavDialog (Bool) 0
</li><li>ShowPathInProjectWindow (Bool) 0
</li><li>ShowRedXOnWire (Bool) 1
</li><li>ShowRTFeaturePacks (Bool) 0
</li><li>showRunAtAnyLoopMenuItem
</li><li>showRunAtAnyLoopMenuItem (Bool) 0
</li><li>showSubVIName (Bool) 0
</li><li>showSystemVIs (Bool) 0
</li><li>showTipStrings (Bool) 1
</li><li>showTipStringsOnDiagram (Bool) 1
</li><li>showTipStringsOnFPControls (Bool) 1
</li><li>showTipStringsOnTerms (Bool) 1
</li><li>showVILibWarnings (Bool) 0
</li><li>showWarnings (Bool) 0
</li><li>showWireDots (Bool) 1
</li><li>showWireGuides (Bool) 1
</li><li>simpleDiagramHelp (Bool) 1
</li><li>simplePopups (Bool) 0
</li><li>SimShowCompanionDiag (Bool) 0
</li><li>skipAutoLaunchVIs (Bool) 0
</li><li>SkipCodeCompaction (Bool) 0
</li><li>skipNavigatorDialog (Bool) 0
</li><li>smartProbesEnabled (Bool) 0
</li><li>smoothGraphMarkers (Bool) 0
</li><li>SnapGridBlockDiagramContrast (I32 ) 0Bh
</li><li>SnapGridBlockDiagramSize (I32 ) 10h
</li><li>SnapGridDrawAsLines (I32 ) 1
</li><li>SnapGridDrawLinesAndDots (Bool) 0
</li><li>SnapGridFrontPanelContrast (I32 ) 0Bh
</li><li>SnapGridFrontPanelSize (I32 ) 0Ch
</li><li>SnapGridMinorDivsInMajor (I32 ) 5
</li><li>SnapGridResizeWhenDropping (Bool) 0
</li><li>SnapGridShowsOnBlockDiagram (Bool) 0
</li><li>SnapGridShowsOnFrontPanel (Bool) 1
</li><li>SnapGridSnapsOnBlockDiagram (Bool) 0
</li><li>SnapGridSnapsOnFrontPanel (Bool) 1
</li><li>SnapToPresetsBD (Bool) 1
</li><li>SnapToPresetsFP (Bool) 1
</li><li>SocketListenBacklog (I32 ) 5
</li><li>SocketRecvBufferSize (I32 ) 0FFFFFFFFh (-1)
</li><li>SocketSendBufferSize (I32 ) 0FFFFFFFFh (-1)
</li><li>SocketSendChunkSize (I32 ) 0FFFFFFFFh (-1)
</li><li>SocketSetReuseAddr (Bool) 0
</li><li>SortPaletteItems (Bool) 0
</li><li>sourceCoercionDot (Colr) 0xFF0000
</li><li>sourceUserCoercionDot (Colr) 0x3366FF
</li><li>statusLogPath (Path) c:\documents and settings\*\local settings\temp\LVStatus.txt
</li><li>StitchInTimeSavesVIs (LStr) 0
</li><li>stressCompactObjHeap (Bool) 0
</li><li>strongLeakWarning (Bool) 1
</li><li>StructuresAutoSizeByDefault (Bool) 1
</li><li>structuresFadeToDiagramBeneath (Bool) 0
</li><li>subTypesEnabled (Bool) 1
</li><li>subTypeSubVIInputsEnabled (Bool) 0
</li><li>SuperSecretPrivateSpecialStuff (Bool) 0
</li><li>suppressFileDlgForMissingVIs (Bool) 0
</li><li>suppressPopups (Bool) 0
</li><li>systemFont (Font) 0
</li><li>TargetHelpMenu (Bool) 0
</li><li>TargetToolsMenu (Bool) 0
</li><li>tcpServer.log (Bool) 0
</li><li>tcpServer.logDetails (Bool) 0
</li><li>tcpServer.logPath (Path)
</li><li>thpri_bgrnd (I32 )
</li><li>thpri_high (I32 )
</li><li>thpri_normal (I32 )
</li><li>thpri_tcrit (I32 )
</li><li>thpri_vhigh (I32 )
</li><li>tileUpDown (Bool) 0
</li><li>timeSeparator (I32 ) 0
</li><li>TimeTriggeredVariableEnabled (Bool) 1
</li><li>titlebarRevision (Bool) 0
</li><li>tmpdir (Path)
</li><li>toolPaletteLoc (Rect)
</li><li>TotallySecretAndPrivateMSNCompanionDiagram (Bool) 0
</li><li>trackTimeout (I32 ) 64h
</li><li>transparentBDFreeLabels (Bool) 0
</li><li>transparentBDLabels (Bool) 1
</li><li>TTFontSmallerMultiplier (I32 ) 1.05
</li><li>TwentyYears (Bool) 0
</li><li>typeDefExternalSignals (Bool) 0
</li><li>UnitDialogGroups (Bool) 1
</li><li>UnveilLVClasses (Bool) 1
</li><li>unwiredDontCareInputsEnabled (Bool) 1
</li><li>UnwiredRecomendedWarning (Bool) 0
</li><li>updateSubVICtrlsFromIUseConsts (Bool) 1
</li><li>UseAbridgedMenus (Bool) 0
</li><li>useAllFKeys (Bool) 1
</li><li>useAlphaBlend (Bool) 1
</li><li>useAsyncDeviceCalls (Bool)
</li><li>UseBitmapClipboard (Bool) 1
</li><li>UseDefaultNumDisplayFormat (Bool) 1
</li><li>useDefaultTimer (Bool) 0
</li><li>useIPInfoInLVEmbedded (Bool) 0
</li><li>useLocaleDecimalPt (Bool)
</li><li>useMargins (Bool) 0
</li><li>UseMarketingSplash (Bool) 0
</li><li>useMaskBlit (Bool) 1
</li><li>useNativeColorPicker (Bool) 1
</li><li>useNativeFileDialog (Bool) 1
</li><li>useNativeSharedVariableNode (Bool) 0
</li><li>useNewPrintHeader (Bool) 1
</li><li>useOCXLicensing (Bool) 0
</li><li>useOldData (Bool) 1
</li><li>useOldDataOnArrays (Bool) 1
</li><li>usePropPageForFormatting (Bool) 1
</li><li>UserDefinedErrorsDir (Path)
</li><li>userVIsAppearFirst (Bool) 0
</li><li>useSingleTree (Bool) 0
</li><li>useTaskBar (Bool) 1
</li><li>useUnicode (Bool)
</li><li>useWindowMenuBars (Bool) 1
</li><li>viCaptionTipStrings (Bool) 1
</li><li>VirtualProtectGeneratedCode (Bool) 1
</li><li>VisaSelectionIndex (I32 ) 1
</li><li>viSearchPath (PLst) 0
</li><li>viTitleInPalettes (Bool) 1
</li><li>warnMin (I32 ) 7D0h
</li><li>weakModDateCheck (Bool) 1
</li><li>WebServer.DirectoryIndex (PStr)
</li><li>WebServer.Enabled (Bool) 0
</li><li>WebServer.ImageCompression (I32 ) 1Ah
</li><li>WebServer.ImageDepth (I32 ) 0
</li><li>WebServer.ImageFullPanel (Bool) 0
</li><li>WebServer.ImageLifeSpan (I32 ) 3Ch
</li><li>WebServer.ImageQuality (I32 ) 50h
</li><li>WebServer.ImageRefresh (I32 ) 7D0h
</li><li>WebServer.ImageType (PStr)
</li><li>WebServer.logDetails (Bool) 0
</li><li>WebServer.LogEnabled (Bool) 0
</li><li>WebServer.LogPath (Path)
</li><li>WebServer.MimeTypes (CPSt)
</li><li>WebServer.Port (I32 ) 50h
</li><li>WebServer.RootPath (Path)
</li><li>WebServer.TcpAccess (CPSt)
</li><li>WebServer.Timeout (I32 ) 3Ch
</li><li>WebServer.ViAccess (CPSt)
</li><li>windowSize (Rect) 0
</li><li>WireRouteTime (I32 ) 32h
</li><li>writeBinarySubtypesEnabled (Bool) 1
</li><li>XNodeDevelopment_LabVIEWInternalTag (Bool) 0
</li><li>XNodeWizardMode (Bool) 0
</li><li>XTraceAll (Bool) 0
</li><li>XTraceXNode (Bool) 0
</li><li>yearFirst (Bool) 0
</li><li>ZCompressLevel (I32 ) 6
</li></ul>

LabVIEW configuration file/Block Diagram

2008-07-17T12:55:47Z

Pbrooks100: Added FancyFPTerms entry - sited source: http://forums.lavag.org/FancyFPTerms-in-LabVIEWini-t725.html

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

{{TOCnestright}}

{{ labviewconfigurationkey
| keyname = allowDragDropFromFileDlg
| example = allowDragDropFromFileDlg=TRUE
| datatype = b
| description = Enables drag and drop functionality from the file dialog to the block diagram of a vi
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 8.5
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This functionality existed in LV 5.0 -> LV 7.1, was removed in LV 8.x, and added back in as an ini setting in 8.5
}}
{{ labviewconfigurationkey
| keyname = autoWireMax
| example = autoWireMax=24
| datatype = i
| description = Maximum distance between nodes for autowiring to be active
| permitted_values = 1 to 232
| default = 16
| LV1 =6
| LV2 =7
| LV3 =8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This setting is only effective if [[#enableAutoWire|enableAutoWire]] is set to TRUE
}}
{{ labviewconfigurationkey
| keyname = autoWireMin
| example = autoWireMin=8
| datatype = i
| description = Minimum distance between nodes for autowiring to be active
| permitted_values = 1 to 232
| default = 4
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = This setting is only effective if [[#enableAutoWire|enableAutoWire]] is set to TRUE
}}
{{ labviewconfigurationkey
| keyname = copyDeleteFPDCOFromFPTerm
| example = copyDeleteFPDCOFromFPTerm=TRUE
| datatype = b
| description = Delete front panel terminals from diagram
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = enableAutoWire
| example = enableAutoWire=FALSE
| datatype = b
| description = Enable Auto Wiring
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = FancyFPTerms
| example = FancyFPTerms=FALSE
| datatype = b
| description = Place front panel terminals as icons
| permitted_values = TRUE or FALSE
| default = (Depends on LV Version)
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = http://forums.lavag.org/FancyFPTerms-in-LabVIEWini-t725.html
}}
{{ labviewconfigurationkey
| keyname = funkyErrClustWire
| example = funkyErrClustWire=FALSE
| datatype = b
| description = Change Error Cluster wires color from the standard cluster pink to a more distinctive brown/green color
| permitted_values = TRUE or FALSE
| default = LabVIEW 5.1, 6.x, 7.x: FALSE, LabVIEW 8.x: TRUE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = inlineSubVIEnabled
| example = inlineSubVIEnabled=FALSE
| datatype = b
| description = Allows the context menu item "Inline SubVI" on any SubVI which inserts the code directly into the block diagram containing the SubVI.
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 = 6
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = maxUndoSteps
| example = maxUndoSteps=50
| datatype = i
| description = Maximum undo steps per VI
| permitted_values = 1 to 99
| default = 8
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showSubVIName
| example = showSubVIName=TRUE
| datatype = b
| description = Show subVI names when dropped
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showTipStringsOnTerms
| example = showTipStringsOnTerms=FALSE
| datatype = b
| description = Show tip-strips over terminals
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showWireDots
| example = showWireDots=TRUE
| datatype = b
| description = Show dots at wire junctions
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =7
| LV2 =8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = showWireGuides
| example = showWireGuides=FALSE
| datatype = b
| description = Show dashed line while wiring
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =4
| LV2 =5
| LV3 =6
| LV4 =7
| LV5 =8
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = structuresFadeToDiagramBeneath
| example = structuresFadeToDiagramBeneath=FALSE
| datatype = b
| description = Makes the diagram of structures semi-transparent so that you can see objects behind them.
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =6
| LV2 =7
| LV3 =8
| LV4 =
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = Enabling this setting will slow down the development environment on large Block Diagrams
}}
{{ labviewconfigurationkey
| keyname = transparentBDLabels
| example = transparentBDLabels=TRUE
| datatype = b
| description = Use transparent name labels
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = UseNumbersForNewVIIconsInLibs
| example = UseNumbersForNewVIIconsInLibs=FALSE
| datatype = b
| description = Tells LabVIEW whether to automatically generate include a number (1-9) in the lower-right corner of each new VI's icon for VIs created inside libraries (.lvlib, .lvclass, .xctl, .lvsc, etc).
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes = LabVIEW 8.5 only
}}
{{ labviewconfigurationkey
| keyname = viCaptionTipStrings
| example = viCaptionTipStrings=FALSE
| datatype = b
| description = Use control captions for subVI tip-strips
| permitted_values = TRUE or FALSE
| default = TRUE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}
{{ labviewconfigurationkey
| keyname = viTitleInPalettes
| example = viTitleInPalettes=TRUE
| datatype = b
| description = Use Window Titles in function palettes
| permitted_values = TRUE or FALSE
| default = FALSE
| LV1 =5
| LV2 =6
| LV3 =7
| LV4 =8
| LV5 =
| LV6 =
| OS1 = w
| OS2 = m
| OS3 = l
| OS4 = u
| notes = None
}}

[[Category:Development Environment|{{PAGENAME}}]]

LabVIEW configuration file/Miscellaneous

2008-05-09T15:29:06Z

Pbrooks100: Key does not appear to work in 7.x

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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 = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype =b
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 8
| LV2 =
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =If set to a non-positive number, then there will be no max. If set to 50 or less, then 50 will be the max
}}
{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
{{ labviewconfigurationkey
| keyname = openInRun
| example =openInRun=TRUE
| datatype =b
| description =When opening VIs in the development environment, open them in ''run mode''
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 3
| LV2 = 4
| LV3 = 5
| LV4 = 6
| LV5 = 7
| LV6 = 8
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = readOnlyLock
| example =readOnlyLock=TRUE
| datatype =b
| description =Treat read-only VIs as locked
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 5
| LV2 = 6
| LV3 = 7
| LV4 = 8
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
}}
{{ labviewconfigurationkey
| keyname = showBDConstName
| example =showBDConstName=TRUE
| datatype =b
| description =Show auto-constant labels
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Unknown

2008-05-09T15:21:13Z

Pbrooks100: MaxHelpDescLength info available; added to Misc.

This is a placeholder for a page that would contain LabVIEW configuration keys that cannot be explained or described because we don't have enough information about what they do.

INI key list from LabVIEW 8.50 (many known ones exist in here, this needs to be sorted and categorized):
<ul><li>"INI_KEY (variable type) default_value"</li></ul>
<ul>
<li>/027usePaletteMenuOnMenuBar (Bool) 1
</li><li>9serviceLocatorLocalOnly (Bool) 0
</li><li>abortMin (I32 ) 1F4h
</li><li>activeX.freeThreaded[0Dh] (Bool) 1
</li><li>ActiveXContainerDefaultInDesignMode (Bool) 0
</li><li>ActiveXMoreContainerOptions (Bool) 0
</li><li>ActiveXPropertyBrowser.AutoHide (Bool) 0
</li><li>addBulletCastInWDTMutation (Bool) 1
</li><li>addProjectOptionsToFileNewDlg (Bool) 0
</li><li>AdviceEnabled (Bool) 0
</li><li>allowDragDropFromFileDlg (Bool) 0
</li><li>AllowManualLoadUnloadCvtFile (Bool) 0
</li><li>allowMultipleInstances (Bool)
</li><li>allowNoLockingForEvents (Bool) 1
</li><li>allowOpenFPOfInstanceVIs (Bool) 0
</li><li>allowPreallocsInDll (Bool) 0
</li><li>AllowRunTimeFontChangeOnPaste (Bool) 0
</li><li>allowSetUnicodeStyle (Bool) 0
</li><li>AlphabetizeVIServerClassMenu (Bool) 1
</li><li>AppDomainSetup_CachePath (Path)
</li><li>AppDomainSetup_DisallowBindingRedirects (Bool) 0
</li><li>AppDomainSetup_DisallowCodeDownload (Bool) 0
</li><li>AppDomainSetup_DisallowPublisherPolicy (Bool) 0
</li><li>AppDomainSetup_DynamicBase (Path)
</li><li>AppDomainSetup_LicenseFile (Path)
</li><li>AppDomainSetup_ShadowCopyFiles (Bool) 1
</li><li>appFont (Font) 0
</li><li>AssistantsUseStrictTypes
</li><li>AssistantsUseStrictTypes (Bool) 0
</li><li>asynchWiresEnabled (I32 ) 0
</li><li>autoDeployOnVIRun (Bool) 1
</li><li>autoerr (Bool) 0
</li><li>autoInsertFeedbackNode (Bool) 1
</li><li>autoPreallocate (Bool) 0
</li><li>autoProbe (Bool) 1
</li><li>autoRouteWires (Bool) 1
</li><li>AutoSaveEnabled (Bool) 1
</li><li>AutoSaveTimeoutMinutes (I32 ) 5
</li><li>AutoSaveTimerEnabled (Bool) 1
</li><li>autoTool (Bool) 1
</li><li>autoTool.allowLabelOnBD (Bool) 0
</li><li>autoTool.allowLabelOnFP (Bool) 0
</li><li>autoTool.changeBoolValsOnBD (Bool) 1
</li><li>autoTool.changeBoolValsOnFP (Bool) 0
</li><li>autoTool.changeNumValsOnBD (Bool) 1
</li><li>autoTool.changeNumValsOnFP (Bool) 1
</li><li>autoTool.doubleClickLabels (Bool) 1
</li><li>autoTool.wireWires (Bool) 0
</li><li>autoToolOn (Bool) 1
</li><li>autoWireMax (I32 ) 20h
</li><li>autoWireMin (I32 ) 04h
</li><li>BDFont (Font) 0
</li><li>BigSavingsFormat (PStr)
</li><li>BitmapFontSmallerMultiplier (I32 ) 1.3
</li><li>blinkBG (Colr) 0FF0000h
</li><li>blinkFG (Colr) 0FFFF00h
</li><li>blinkSpeed (I32 ) 3E8h
</li><li>BuildPDAPrc (Bool) 1
</li><li>CallistoAutoReload (Bool) 1
</li><li>CallistoSimpleWires (Bool) 0
</li><li>callLibNodeMayHaveLVClassParams (Bool) 0
</li><li>CBoxCommentColor (Colr) 7F5Fh
</li><li>CBoxConstantColor (Colr) 0
</li><li>CBoxDataTypeColor (Colr) 09Dh
</li><li>CBoxDefaultColor (Colr) 0
</li><li>CBoxExternalEditorPath (Path)
</li><li>CBoxKeywordColor (Colr) 55003Fh
</li><li>CBoxModifierColor (Colr) 045h
</li><li>CBoxPreprocessorColor (Colr) 055h
</li><li>CBoxStringColor (Colr) 0FFh
</li><li>CBoxTabSize (I32 ) 8
</li><li>CCodeGenDir (Path) 0
</li><li>CDIntervalTicks (I32 ) 7
</li><li>CGenBuildApp (Bool) 1
</li><li>CGenDownloadApp (Bool) 1
</li><li>CGenLaunchAction (I32 ) 0
</li><li>checkActiveXLibs (Bool) 0
</li><li>checkAvailDiskSpace (Bool) 1
</li><li>checkFontSize (Bool) 0
</li><li>CheckHighWaterMarks (Bool)
</li><li>checkQElements (Bool) 0
</li><li>ClassBrowserEnabled (Bool) 1
</li><li>cleanupVisa (Bool) 0
</li><li>closeConfVIOnBDClose (Bool) 1
</li><li>coerceFromVariant (Bool) 0
</li><li>coercionDotmColor (Colr) 0xFF0000
</li><li>colorHistoryItemA (Colr) 3452540h
</li><li>colorHistoryItemB (Colr) 3452540h
</li><li>colorHistoryItemC (Colr) 3452540h
</li><li>colorHistoryItemD (Colr) 3452540h
</li><li>colorHistoryItemE (Colr) 3452540h
</li><li>colorHistoryItemF (Colr) 3452540h
</li><li>colorHistoryItemG (Colr) 3452540h
</li><li>colorHistoryItemH (Colr) 3452540h
</li><li>colorHistoryItemI (Colr) 3452540h
</li><li>colorHistoryItemJ (Colr) 3452540h
</li><li>colorHistoryItemK (Colr) 3452540h
</li><li>colorPrinting (Bool) 1
</li><li>colorUserItem (Colr) 35A368Ch
</li><li>compileOptimizeFlags (I32 ) 5
</li><li>confDiagEnabled (Bool) 0
</li><li>ContextHelpLoc (Rect)
</li><li>controlPropertyPages (Bool) 1
</li><li>convert4xData (Bool) 1
</li><li>copyDeleteFPDCOFromFPTerm (Bool) 1
</li><li>createDefaultProject (Bool) 0
</li><li>createLogFile (Bool)
</li><li>ctlEditNoQuestions (Bool) 0
</li><li>cursor.background (Colr) 0FFFFFFh
</li><li>cursor.foreground (Colr) 0
</li><li>CustomShortcuts (ECPS) 1
</li><li>DAbortDialog (Bool)
</li><li>dateDayFirst (Bool) 0
</li><li>dateSeparator (I32 ) 0
</li><li>DbgSkipAssertIdentsAndVIsMatch (Bool) 1
</li><li>DebugDlgSkipList (CPSt)
</li><li>debugging (Bool)
</li><li>debugkeys (Bool)
</li><li>DebugLogSkipList (CPSt)
</li><li>DebugSimScripting (Bool) 0
</li><li>debugVHDL (Bool) 0
</li><li>defaultControlFormat (PStr)
</li><li>defaultControlStyle (I32 ) 0
</li><li>DefaultDataFileLocation (Path)
</li><li>defaultdir (Path) 0
</li><li>defaultErrorHandlingForNewVIs (Bool) 1
</li><li>defaultIndicatorFormat (PStr)
</li><li>DefaultLabelLockBD (Bool) 0
</li><li>DefaultLabelLockFP (Bool) 0
</li><li>DefaultLabelPositionBD (I32 ) 0
</li><li>DefaultLabelPositionFP (I32 ) 0
</li><li>DefaultPingDelay (I32 ) 2710h
</li><li>DefaultPingTimeout (I32 ) 2710h
</li><li>diagram.background (Colr) 0xFFFFFF
</li><li>diagram.primColor (Colr) 0xFFFFCC
</li><li>DialogBoolsOnlyUseWindowsKeys (Bool) 1
</li><li>dialogFont (Font) 0
</li><li>diff.circles (Bool) 1
</li><li>diff.showMatches (Bool) 0
</li><li>diff.tileVert (Bool) 1Ah
</li><li>disableBatchAdd (Bool) 0
</li><li>disableCrossLinkWarningDlgs (I32 ) 3Fh
</li><li>disableMenuEffects (Bool) 0
</li><li>DisableTargetSyntaxChecking (Bool) 0
</li><li>dithering (Bool) 0
</li><li>DNSLookupEnabled (Bool) 1
</li><li>dontGiveInstanceVIsTitles (Bool) 0
</li><li>DontShowProjectAddDialog (Bool) 0
</li><li>DontShowProjectAddDialog2 (Bool) 0
</li><li>DontShowProjectAddDialogDoNotAdd (Bool) 0
</li><li>DontShowProjectRemoveDialog (Bool) 0
</li><li>DontShowProjectRemoveDialogNonFile (Bool) 0
</li><li>DontUseAltTab (Bool) 0
</li><li>doObjPathChecking (Bool) 1
</li><li>doubleClickToEditControl (Bool) 0
</li><li>DPrintfLogging (Bool) 0
</li><li>DPrintfToFile (Bool)
</li><li>drawFPTermArrow (Bool) 1
</li><li>DropSubsystemsAsXNode (Bool) 1
</li><li>dropThroughClicks (Bool) 1
</li><li>DSWriteTimeout (I32 ) ?
</li><li>dumpLoadLog (Bool) 0
</li><li>DWarnDialog (Bool) 0
</li><li>DWarnDialogMultiples (Bool) 0
</li><li>DWarnLogging (Bool) 1
</li><li>editInMultipleContexts (Bool) 1
</li><li>editor.liveUpdates (Bool) 0
</li><li>editor.smartWiring (Bool) 0
</li><li>editRecentPaths (PLst) 0
</li><li>editRTMenusFromRsrc (Bool) 0
</li><li>EnableAutomaticErrorHandling (Bool) 1
</li><li>EnableAutomaticErrorHandlingRT (Bool) 0
</li><li>enableAutoScales (Bool) 1
</li><li>enableAutoWire (Bool) 1
</li><li>enableCustomInterface (Bool) 1
</li><li>enableGroupLock (Bool) 1
</li><li>EnableIGL (Bool) 0
</li><li>EnableIGLStressTest (Bool) 0
</li><li>enableMultiScales (Bool) 1
</li><li>EnableMultiThreadedLoad (Bool) 0
</li><li>enableRelativeSharedVariableNodes (Bool) 1
</li><li>enableShellExtension (Bool) 1
</li><li>EnableStrictTypedefConstantConfiguration (Bool) 0
</li><li>EnableTimeDataNodeHiddenElements (Bool) 0
</li><li>EnableTimedLoops (Bool) 1
</li><li>ESys.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.DAQ.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.DAQ.High (I32 ) 144E07Bh
</li><li>ESys.DAQ.Normal (I32 ) 144E07Bh
</li><li>ESys.DAQ.TCritical (I32 ) 144E07Bh
</li><li>ESys.DAQ.VHigh (I32 ) 144E07Bh
</li><li>ESys.High (I32 ) 144E07Bh
</li><li>ESys.instrument.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.instrument.High (I32 ) 144E07Bh
</li><li>ESys.instrument.Normal (I32 ) 144E07Bh
</li><li>ESys.instrument.TCritical (I32 ) 144E07Bh
</li><li>ESys.instrument.VHigh (I32 ) 144E07Bh
</li><li>ESys.Normal (I32 ) 144E07Bh
</li><li>ESys.other1.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.other1.High (I32 ) 144E07Bh
</li><li>ESys.other1.Normal (I32 ) 144E07Bh
</li><li>ESys.other1.TCritical (I32 ) 144E07Bh
</li><li>ESys.other1.VHigh (I32 ) 144E07Bh
</li><li>ESys.other2.Bgrnd (I32 ) 144E07Bh
</li><li>ESys.other2.High (I32 ) 144E07Bh
</li><li>ESys.other2.Normal (I32 ) 144E07Bh
</li><li>ESys.other2.TCritical (I32 ) 144E07Bh
</li><li>ESys.other2.VHigh (I32 ) 144E07Bh
</li><li>ESys.StdNParallel (I32 ) 4
</li><li>ESys.TCritical (I32 ) 144E07Bh
</li><li>ESys.VHigh (I32 ) 144E07Bh
</li><li>EventLogging.EnableVITracing (Bool) 0
</li><li>examplesDir (Path) 0
</li><li>ExecEngineSelectPrompt (Bool) 0
</li><li>execPalette.background (Colr) 1000030h
</li><li>execPalette.foreground (Colr) 0
</li><li>execRecentPaths (PLst) 0
</li><li>execThreadStackOffsetIncr (I32 ) 40h
</li><li>exposedTypeDefsEnabled (Bool) 1
</li><li>expressLeaveWizardsOpenAfterLaunch (Bool) 0
</li><li>ExternalNodeDebugging (Bool) 0
</li><li>ExternalNodesEnabled (Bool) 0
</li><li>extFuncCatching (I32 ) 1
</li><li>extFuncExtendedOptionsEnabled (Bool) 0?
</li><li>extFuncGenNoWrapperEnabled (Bool) 0
</li><li>fadeEphemeralWires (Bool) 0
</li><li>FancyFPTerms (Bool) 1
</li><li>fastPreSCFlatGeneration (Bool) 0
</li><li>FilterExec (Bool) 1
</li><li>find.findTextFlags (I32 ) 6C6F6F42h "Bool"
</li><li>find.nodeRsrcID (I32 ) 41Ah
</li><li>find.searchStr (PStr) 0
</li><li>find.viListFlags (I32 ) 0
</li><li>findIPPathEnabled (Bool) 1
</li><li>FindSpaceCreateZone (I32 ) 96h
</li><li>FindSpaceOnCreate (Bool) 1
</li><li>firstDiffMonitor (I32 ) 6C6F6F42h "Bool"
</li><li>FlatLibChain (Bool) 1
</li><li>flushDrawing (Bool) 1
</li><li>formulaBoxPrecision (PStr) ????
</li><li>FPDSConnectTimeout (I32 ) 61A8h
</li><li>FPFont (Font) 0
</li><li>FPUpdateRate (I32 ) 0Ah
</li><li>funkyErrClustWire (Bool) 1
</li><li>FXPDefaultIntWordLength (I32 ) 10h
</li><li>FXPDefaultSigned (Bool) 1
</li><li>FXPDefaultWordLength (I32 ) 20h
</li><li>gCachedArc.extreme (Bool) 1
</li><li>genDualInterface (Bool) 1
</li><li>graphReadsAttributes (Bool) 1
</li><li>grayOutMethod (PStr)
</li><li>growSubVI.defaultStyle (I32 ) 29h
</li><li>growSubVI.enabled (Bool) 0
</li><li>HardWaitTimeCritical (Bool)
</li><li>HardWaitVeryHigh (Bool)
</li><li>help.showconnums (Bool) 0
</li><li>HelpServerEnabled (Bool) 0
</li><li>helpServerEnabled (Bool) 1
</li><li>hideEmptySubPalettes (Bool) 0
</li><li>hideRootWindow (Bool) 0
</li><li>hierarchy.stateFlags (I32 ) 47h
</li><li>HierarchyWindow.ProjectView (Bool) 1
</li><li>HierarchyWindow.ShowPrivateApp (Bool) 0
</li><li>HierarchyWindow.ZeroUserProjectNoProjectView (Bool) 1
</li><li>HiliteExecutionPride (Bool) 0
</li><li>HiliteExecutionWhosePride (Path) 0
</li><li>history.alwaysRecordChange (Bool) 0
</li><li>history.generateComments (Bool) 0
</li><li>history.promptAtClose (Bool) 0
</li><li>history.promptAtSave (Bool) 0
</li><li>history.whereToGetName (PStr) 0
</li><li>honorOffScreenSettings (Bool) 1
</li><li>hotMenus (Bool) 1
</li><li>hour24 (Bool) 0
</li><li>i386_AlignedLabels (Bool)
</li><li>i386_CacheAlign (I32 ) 40h
</li><li>i386_CacheAlign (I32 ) 40h
</li><li>IconFont (Font) 0xFFFFFF ???
</li><li>ignoreHelpAndProjDirs (Bool) 0
</li><li>imagesCompressedInMem (Bool) 0
</li><li>independentImageDepth (I32 ) 0
</li><li>inlineSubVIEnabled (Bool) 0
</li><li>inplaceRefOutputsEnabled (I32 ) 1
</li><li>int64Enabled (Bool) 1
</li><li>InternetToolkitInstalled (Bool) 0
</li><li>ipConstantsEnabled (Bool) 0
</li><li>IsFirstLaunch (Bool) 1
</li><li>kctCPDADirPath (Path) 0
</li><li>keepDotNetDomainAlive (Bool) 0
</li><li>keepIntensityBitmap (Bool) 0
</li><li>keyboardAccelerateSave (Bool) 0
</li><li>LastErrorListSize (Rect) 0
</li><li>LaunchConfigurationPageAfterDropExpressBlock (Bool) 1
</li><li>launchNewWorkspaceOnStart (Bool) 0
</li><li>LaunchScreenTextBGColor (Colr) 0FFBB00h
</li><li>LaunchTimeBenchmarking (Bool) 0
</li><li>leftClickPopupPalette (Bool) 0
</li><li>libdir (Path) 0
</li><li>ListboxSelectionStyle (PStr) 0???
</li><li>ListboxSelectionVersion (PStr) 0???
</li><li>loadAlwaysSearches (fMv03) 1
</li><li>LoadGWSAtStart (Bool) 0
</li><li>LocalHost (Path) 0
</li><li>LogFileSaved (Bool) 0
</li><li>LVClassOutputsDynamicByDefault (Bool) 1
</li><li>LVdebugKeys (Bool) 0
</li><li>lvPictImagesSavedCompressed (Bool) 1
</li><li>LVTargets (Path) 0
</li><li>marginB (I32 ) 0
</li><li>marginL (I32 ) 0
</li><li>marginR (I32 ) 0
</li><li>marginT (I32 ) 0
</li><li>marginUnitInch (Bool) 1
</li><li>mathScriptPath (PLst)
</li><li>MaxDPrintfsLogged (I32 )
</li><li>MaxDWarnsLog (I32 )
</li><li>maxUndoSteps (I32 ) 8
</li><li>maxVISizeForMemoryUncompress (I32 ) 400000h
</li><li>memoryChecking (Bool)
</li><li>menu.1 (Path)
</li><li>menu.background (Colr) 100002Eh
</li><li>menu.foreground (Colr) 100002Dh
</li><li>menubar.background (Colr) 1000030h
</li><li>menubar.foreground (Colr) 100002Fh
</li><li>MenuMRUItems (LStr) 0
</li><li>mergeAdjVirtualAllocs (Bool)
</li><li>MinMNGFrameDelay (I32 ) 0
</li><li>moveDefaultContextVIsToProjContext (Bool) 0
</li><li>MRUFolders (Bool) 0
</li><li>mutateToPeriodDecimalPoint (I32 ) 0
</li><li>netconn (Bool) 1
</li><li>NISecurityTimeout (I32 ) 2710h
</li><li>noBoxAroundName (Bool) 1
</li><li>nodeBreakPointMenuItem (Bool) 0
</li><li>nonDirectionalSignals (Bool) 0
</li><li>NoSavePromptForReadonlyLocked (Bool) 0
</li><li>NoTypeBanner (Bool)
</li><li>numStatusItemsToLog (I32 ) 0
</li><li>offscreenUpdates (Bool) 1
</li><li>OldStyleSave (Bool) 0
</li><li>ole.AuthnLevel (I32 )
</li><li>ole.ImpLevel (I32 )
</li><li>OleVariantList (Bool) 0
</li><li>openInRun (Bool) 0
</li><li>overanxiousMemoryDeallocation (Bool) 0
</li><li>overrideLoadWarningDialog (Bool) 0
</li><li>paintPixmap (Bool) 0
</li><li>paletteAsyncLoad (Bool) 1
</li><li>PaletteHidddenControlCategories_LocalHost (LStr)
</li><li>PaletteHidddenFunctionlCategories_LocalHost (LStr)
</li><li>paletteLazyLoad (Bool) 0
</li><li>PaletteNavBarStyle (PStr)
</li><li>paletteStyle (PStr)
</li><li>panel.background (Colr) 0B3B3B3h
</li><li>PathManagerImplementation (P255)
</li><li>pinPlotLegendLeft (Bool) 0
</li><li>playAnimatedImages (Bool) 1
</li><li>PlotHitThreshold (I32 ) 2
</li><li>PolySelectorEnabledAtDrop (Bool) 1
</li><li>populateLibs (Bool) 0
</li><li>postScriptLevel2 (Bool) 1
</li><li>postScriptPrinting (Bool) 0
</li><li>preAllocateEnabled (Bool) 1
</li><li>preAllocateStringsUIEnabled (Bool) 0
</li><li>preAllocateUIEnabled (Bool) 0
</li><li>preloadSCScriptingVIs (Bool) 0
</li><li>preloadSimScriptingVIs (Bool) 1
</li><li>prettyExecHilite (Bool) 1
</li><li>printCGenFileAndLineNumbers (Bool) 0
</li><li>printerDithering (Bool) 0
</li><li>printUsingBitmap (Bool) 0
</li><li>ProbeDefaultCache (PLst)
</li><li>ProbeIniCache_8.5 (PLst)
</li><li>project.EditorMode (PStr) 0
</li><li>project.maximizeFrame (Bool) 1
</li><li>project.subduedMDIFrame (Bool) 1
</li><li>project.windowsStayOutAfterRun (Bool) 0
</li><li>projectDebugPumpOSMsgs (Bool) 0
</li><li>projectInternalOptions (I32 ) 0C0h
</li><li>projectProviderSearchPaths
</li><li>projectProviderSearchPaths (PLst)
</li><li>promoteDWarnInternals (Bool)
</li><li>promptToSaveNewProjects (Bool) 0
</li><li>PSPFPLEDVisibleDefault (Bool) 1
</li><li>PumpOSMsgsinCallback (Bool) 0
</li><li>PWNT_AlignedLabels (Bool)
</li><li>PWNT_CacheAlign (I32 )
</li><li>quickMenuProperties (Bool) 0
</li><li>readOnlyLock (Bool) 0
</li><li>RecentFiles.maxNum (I32 ) 0Ah
</li><li>RecentFiles.pathList (PLst) 0
</li><li>RecentFiles.projectPathList (PLst) 0
</li><li>RecentFiles.showFullPath (Bool) 0
</li><li>RecentTemplates.maxNum (I32 ) 0Ah
</li><li>RecentTemplates.pathList (PLst) 0
</li><li>RecompileOnLibChange
</li><li>recursiveTypesEnabled (Bool) 0
</li><li>RegisterExtensions (Bool) 1
</li><li>RelaxQualifiedNameMatching (Bool) 0
</li><li>RemotePanel.InactiveCloseTimeout (I32 ) 0
</li><li>RemotePanel.InactivePingTimeout (I32 ) 0
</li><li>RemotePanel.InactiveTimeoutEnabled (Bool) 0
</li><li>RemotePanel.MaxMsgBacklog (I32 ) 0
</li><li>RemotePanel.MaxMsgBacklogInSecs (I32 ) 0
</li><li>RemotePanel.NetloadLogInterval (I32 ) 0
</li><li>RemotePanel.NetloadLogInterval (I32 ) 0
</li><li>RemotePanel.NetloadLogNumOfSamples (I32 ) 0
</li><li>RemotePanel.NetloadLogNumOfSamples (I32 ) 0
</li><li>RemotePanel.ServerTimeoutInSecs (I32 ) 0
</li><li>RemotePanel.ServerTimeoutInSecs (I32 ) 0
</li><li>RemotePanel.VIControlTimeLimit (I32 ) 0
</li><li>ReportMovingVIs (Bool) 1
</li><li>reqdTermsByDefault (Bool) 0
</li><li>requireAutoTool (Bool) 1
</li><li>resettingDlgDelay (I32 ) 44Ch
</li><li>returnKeyAction (Bool) 0
</li><li>RTTarget.ApplicationPath (Path) 0
</li><li>RTTarget.EnableFileSharing (Bool) 0
</li><li>RTTarget.IPAccess (CPSt) 1: ""
</li><li>RTTarget.LaunchAppAtBoot (Bool) 0
</li><li>RTTarget.VIPath (Path) 0
</li><li>runSCSemanticCheck (Bool) 1
</li><li>rviDir (Path) 0
</li><li>SaveBackIntoOriginalFile (Bool) 1
</li><li>SaveChanges_ApplyToAll (Bool) 0
</li><li>SaveChanges_ExpandedAffectedFileList (Bool) 1
</li><li>saveFloaterLocations (Bool) 1
</li><li>ScaledToFitVisible (Bool) 0
</li><li>SCCConfigData (LStr)
</li><li>SCCDisplayOnlySelected (Bool) 1
</li><li>SCCDisplayWarningIfCheckedOut (Bool) 1
</li><li>SCCIncludeInstrLibInGetDependents (Bool) 1
</li><li>SCCIncludeVILibInGetDependents (Bool) 1
</li><li>SCCLocalPath (Path)
</li><li>SCCProjectName (LStr) 0
</li><li>SCCPromptToAddToAddSubVIs (Bool) 1
</li><li>SCCPromptToAddToProject (Bool) 1
</li><li>SCCPromptToCheckOut (Bool) 1
</li><li>SCCProviderLocation (LStr)
</li><li>SCCProviderName (LStr)
</li><li>SCCSelectCallersWhenCheckedOut (Bool) 1
</li><li>SCCSelectHierarchyWhenAdd (Bool) 1
</li><li>SCCUseDialogBox (Bool) 0
</li><li>Scripting_LabVIEWInternalTag (Bool) 0
</li><li>scriptNodeWait (I32 ) 0
</li><li>scrollbar.background (Colr) 1000032h
</li><li>scrollbar.foreground (Colr) 1000031h
</li><li>scrollGraphCursors (Bool) 1
</li><li>scrollingStripCharts (Bool) 0
</li><li>secondDiffMonitor (I32 ) 1
</li><li>security.keyboardACL (LStr) 0
</li><li>security.loginMode (Bool) 0
</li><li>security.SVEDomain (LStr) 0
</li><li>security.SVELoginMode (Bool) 0
</li><li>security.SVEUsername (LStr) 0
</li><li>server.tcp.port (I32 ) 0
</li><li>serviceLocatorEnabled (Bool) 1
</li><li>serviceLocatorTimeout (I32 ) 1F4h
</li><li>showAllPalettes (Bool) 0
</li><li>ShowAllVIsInErrorWindow (Bool) 0
</li><li>showBDConstName (Bool) 0
</li><li>showConfVIFrontPanel (Bool) 0
</li><li>showDatatypeOnFancyTerms (Bool) 1
</li><li>showDefaultErrorHandlingDebugBtn (Bool) 0
</li><li>ShowDSCFeaturePacks (Bool) 0
</li><li>showEmptyHistoryEntries (Bool) 0
</li><li>showExePathInWindowTitle (Bool) 0
</li><li>showFullPathOfInstanceVIs (Bool) 0
</li><li>showGridTipStrips (Bool) 1
</li><li>ShowGWS (Bool) 0
</li><li>ShowHiddenLibraryItems (Bool) 0
</li><li>showHiddenUserDefinedRefnumClasses (Bool) 0
</li><li>showNoNavDialog (Bool) 0
</li><li>ShowPathInProjectWindow (Bool) 0
</li><li>ShowRedXOnWire (Bool) 1
</li><li>ShowRTFeaturePacks (Bool) 0
</li><li>showRunAtAnyLoopMenuItem
</li><li>showRunAtAnyLoopMenuItem (Bool) 0
</li><li>showSubVIName (Bool) 0
</li><li>showSystemVIs (Bool) 0
</li><li>showTipStrings (Bool) 1
</li><li>showTipStringsOnDiagram (Bool) 1
</li><li>showTipStringsOnFPControls (Bool) 1
</li><li>showTipStringsOnTerms (Bool) 1
</li><li>showVILibWarnings (Bool) 0
</li><li>showWarnings (Bool) 0
</li><li>showWireDots (Bool) 1
</li><li>showWireGuides (Bool) 1
</li><li>simpleDiagramHelp (Bool) 1
</li><li>simplePopups (Bool) 0
</li><li>SimShowCompanionDiag (Bool) 0
</li><li>skipAutoLaunchVIs (Bool) 0
</li><li>SkipCodeCompaction (Bool) 0
</li><li>skipNavigatorDialog (Bool) 0
</li><li>smartProbesEnabled (Bool) 0
</li><li>smoothGraphMarkers (Bool) 0
</li><li>SnapGridBlockDiagramContrast (I32 ) 0Bh
</li><li>SnapGridBlockDiagramSize (I32 ) 10h
</li><li>SnapGridDrawAsLines (I32 ) 1
</li><li>SnapGridDrawLinesAndDots (Bool) 0
</li><li>SnapGridFrontPanelContrast (I32 ) 0Bh
</li><li>SnapGridFrontPanelSize (I32 ) 0Ch
</li><li>SnapGridMinorDivsInMajor (I32 ) 5
</li><li>SnapGridResizeWhenDropping (Bool) 0
</li><li>SnapGridShowsOnBlockDiagram (Bool) 0
</li><li>SnapGridShowsOnFrontPanel (Bool) 1
</li><li>SnapGridSnapsOnBlockDiagram (Bool) 0
</li><li>SnapGridSnapsOnFrontPanel (Bool) 1
</li><li>SnapToPresetsBD (Bool) 1
</li><li>SnapToPresetsFP (Bool) 1
</li><li>SocketListenBacklog (I32 ) 5
</li><li>SocketRecvBufferSize (I32 ) 0FFFFFFFFh (-1)
</li><li>SocketSendBufferSize (I32 ) 0FFFFFFFFh (-1)
</li><li>SocketSendChunkSize (I32 ) 0FFFFFFFFh (-1)
</li><li>SocketSetReuseAddr (Bool) 0
</li><li>SortPaletteItems (Bool) 0
</li><li>sourceCoercionDot (Colr) 0xFF0000
</li><li>sourceUserCoercionDot (Colr) 0x3366FF
</li><li>statusLogPath (Path) c:\documents and settings\*\local settings\temp\LVStatus.txt
</li><li>StitchInTimeSavesVIs (LStr) 0
</li><li>stressCompactObjHeap (Bool) 0
</li><li>strongLeakWarning (Bool) 1
</li><li>StructuresAutoSizeByDefault (Bool) 1
</li><li>structuresFadeToDiagramBeneath (Bool) 0
</li><li>subTypesEnabled (Bool) 1
</li><li>subTypeSubVIInputsEnabled (Bool) 0
</li><li>SuperSecretPrivateSpecialStuff (Bool) 0
</li><li>suppressFileDlgForMissingVIs (Bool) 0
</li><li>suppressPopups (Bool) 0
</li><li>systemFont (Font) 0
</li><li>TargetHelpMenu (Bool) 0
</li><li>TargetToolsMenu (Bool) 0
</li><li>tcpServer.log (Bool) 0
</li><li>tcpServer.logDetails (Bool) 0
</li><li>tcpServer.logPath (Path)
</li><li>thpri_bgrnd (I32 )
</li><li>thpri_high (I32 )
</li><li>thpri_normal (I32 )
</li><li>thpri_tcrit (I32 )
</li><li>thpri_vhigh (I32 )
</li><li>tileUpDown (Bool) 0
</li><li>timeSeparator (I32 ) 0
</li><li>TimeTriggeredVariableEnabled (Bool) 1
</li><li>titlebarRevision (Bool) 0
</li><li>tmpdir (Path)
</li><li>toolPaletteLoc (Rect)
</li><li>TotallySecretAndPrivateMSNCompanionDiagram (Bool) 0
</li><li>trackTimeout (I32 ) 64h
</li><li>transparentBDFreeLabels (Bool) 0
</li><li>transparentBDLabels (Bool) 1
</li><li>TTFontSmallerMultiplier (I32 ) 1.05
</li><li>TwentyYears (Bool) 0
</li><li>typeDefExternalSignals (Bool) 0
</li><li>UnitDialogGroups (Bool) 1
</li><li>UnveilLVClasses (Bool) 1
</li><li>unwiredDontCareInputsEnabled (Bool) 1
</li><li>UnwiredRecomendedWarning (Bool) 0
</li><li>updateSubVICtrlsFromIUseConsts (Bool) 1
</li><li>UseAbridgedMenus (Bool) 0
</li><li>useAllFKeys (Bool) 1
</li><li>useAlphaBlend (Bool) 1
</li><li>useAsyncDeviceCalls (Bool)
</li><li>UseBitmapClipboard (Bool) 1
</li><li>UseDefaultNumDisplayFormat (Bool) 1
</li><li>useDefaultTimer (Bool) 0
</li><li>useIPInfoInLVEmbedded (Bool) 0
</li><li>useLocaleDecimalPt (Bool)
</li><li>useMargins (Bool) 0
</li><li>UseMarketingSplash (Bool) 0
</li><li>useMaskBlit (Bool) 1
</li><li>useNativeColorPicker (Bool) 1
</li><li>useNativeFileDialog (Bool) 1
</li><li>useNativeSharedVariableNode (Bool) 0
</li><li>useNewPrintHeader (Bool) 1
</li><li>useOCXLicensing (Bool) 0
</li><li>useOldData (Bool) 1
</li><li>useOldDataOnArrays (Bool) 1
</li><li>usePropPageForFormatting (Bool) 1
</li><li>UserDefinedErrorsDir (Path)
</li><li>userVIsAppearFirst (Bool) 0
</li><li>useSingleTree (Bool) 0
</li><li>useTaskBar (Bool) 1
</li><li>useUnicode (Bool)
</li><li>useWindowMenuBars (Bool) 1
</li><li>viCaptionTipStrings (Bool) 1
</li><li>VirtualProtectGeneratedCode (Bool) 1
</li><li>VisaSelectionIndex (I32 ) 1
</li><li>viSearchPath (PLst) 0
</li><li>viTitleInPalettes (Bool) 1
</li><li>warnMin (I32 ) 7D0h
</li><li>weakModDateCheck (Bool) 1
</li><li>WebServer.DirectoryIndex (PStr)
</li><li>WebServer.Enabled (Bool) 0
</li><li>WebServer.ImageCompression (I32 ) 1Ah
</li><li>WebServer.ImageDepth (I32 ) 0
</li><li>WebServer.ImageFullPanel (Bool) 0
</li><li>WebServer.ImageLifeSpan (I32 ) 3Ch
</li><li>WebServer.ImageQuality (I32 ) 50h
</li><li>WebServer.ImageRefresh (I32 ) 7D0h
</li><li>WebServer.ImageType (PStr)
</li><li>WebServer.logDetails (Bool) 0
</li><li>WebServer.LogEnabled (Bool) 0
</li><li>WebServer.LogPath (Path)
</li><li>WebServer.MimeTypes (CPSt)
</li><li>WebServer.Port (I32 ) 50h
</li><li>WebServer.RootPath (Path)
</li><li>WebServer.TcpAccess (CPSt)
</li><li>WebServer.Timeout (I32 ) 3Ch
</li><li>WebServer.ViAccess (CPSt)
</li><li>windowSize (Rect) 0
</li><li>WireRouteTime (I32 ) 32h
</li><li>writeBinarySubtypesEnabled (Bool) 1
</li><li>XNodeDevelopment_LabVIEWInternalTag (Bool) 0
</li><li>XNodeWizardMode (Bool) 0
</li><li>XTraceAll (Bool) 0
</li><li>XTraceXNode (Bool) 0
</li><li>yearFirst (Bool) 0
</li><li>ZCompressLevel (I32 ) 6
</li></ul>

LabVIEW configuration file/Miscellaneous

2008-05-09T15:17:41Z

Pbrooks100:

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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 = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype =b
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| default =8000
| LV1 = 7
| LV2 = 8
| 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 = 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 = 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
}}

[[Category:Development Environment]]

LabVIEW configuration file/Miscellaneous

2008-05-09T15:16:57Z

Pbrooks100: MaxHelpDescLength added; see http://forums.lavag.org/Context-Help-truncated-t10895.html&p=45473#entry45473

This is a list of Miscellaneous LabVIEW ini File settings.

{{ 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 = dropThroughClicks
| example =dropThroughClicks=FALSE
| datatype =b
| description =Allow drop-through clicks
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodesEnabled
| example =ExternalNodesEnabled=FALSE
| datatype =b
| description =Enables use of [[External Nodes]]
| permitted_values =TRUE or FALSE
| default =6.x?, 7.x: TRUE 8.x: FALSE
| LV1 = 6.x?
| LV2 = 7
| LV3 = 8
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = ExternalNodeDebugging
| example =ExternalNodeDebugging=FALSE
| datatype =b
| description =Shows External Nodes for what they are: sequence diagrams
| permitted_values =TRUE or FALSE
| default =FALSE
| LV1 = 7
| LV2 = 8
| LV3 =
| LV4 =
| LV5 =
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = hotMenus
| example =hotMenus=FALSE
| datatype =b
| description =Use hot menus
| permitted_values =TRUE or FALSE
| default =TRUE
| LV1 = 4
| LV2 = 5
| LV3 = 6
| LV4 = 7
| LV5 = 8
| LV6 =
| OS1 =w
| OS2 =m
| OS3 =l
| OS4 =
| notes =None
}}
{{ labviewconfigurationkey
| keyname = MaxHelpDescLength
| example =MaxHelpDescLength=8000
| datatype =i
| description =Maximum number of characters that will be displayed before truncation in the Context Help
| permitted_values =TRUE or FALSE
| default =8000
| LV1 = 7
| LV2 = 8
| 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 = 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 = 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
}}

[[Category:Development Environment]]

Action engine

2008-01-04T22:37:18Z

Pbrooks100: Redirecting to Functional global variable

#REDIRECT [[Functional global variable]]

Functional global variable

2008-01-04T19:45:31Z

Pbrooks100: removed link to delteted "Action Engines" entry

{{TOCnestright}}
Functional Globals are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals (FGs) most often make use of uninitialized shift registers (USRs). USRs are shift registers that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

==Alternative Nomenclature==
Functional Globals are known by various names among LabVIEW programmers.
*LV2 globals – because LV2 supported uninitialized shift registers
*USR globals – since most FGs make use of uninitialized shift registers
* VIG - "VI Global" as the VI performs the functionality of a global
*Action engines – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

==Structure==
The most common form of a Functional Global is a [[While Loop]] with a TRUE wired to the stop condition. This forces the loop to terminate after just one execution, meaning the while loop is only used to provide a place to put USRs. A [[For Loop]] could also be used with a constant wired to the count terminal. Another method is to use a single-element queue to store the data, though this requires more mouse clicks to implement. The performance of each of these is very close and most likely will vary a little from computer to computer.

[[Image:Simple_FG.PNG|frame|center|Simple Functional Global using a While Loop]]

In order to specify what action to perform, an [[enumerated type]] is often used as an input to the Functional Global. Other methods are possible (Booleans, First Call?, etc.), but an enumerated type provides for a readable, extensible list of actions. Furthermore, saving the enumerated type as a typedef control makes any changes to the list automatically update wherever the Functional Global is used in the code. The ‘action’ input is fed to a case structure which contains the code to implement for each of the defined actions.

For more complex situations, multiple actions can be performed on a single call to the FG. This can be a straightforward [[state machine]], or it can allow for different actions based on the data received or on the existence of resources, etc.

The data in a Functional Global could be of any type, but very often there will be several data elements in a single FG. It is helpful to group the data into a cluster to limit the number of wires entering and leaving the FG. Designing the data structures and how you cluster your data should be done early on, rather than haphazardly growing your clusters as you grow your program.

In order to deal with varying input requirements on the different actions, one can create ‘wrappers’ around the Functional Global that allow for different inputs to be required. This also gives the benefit of being able to search your code for certain actions as you can search for a specific VI, but not a specific enumerated type’s value.

==Uses==
The primary use of Functional Globals is to provide data sharing across an entire project, both horizontally and vertically. Horizontal sharing means multiple top-level VIs running autonomously can all have access to the same data. Vertical sharing means that subVIs at any depth will have access to the data without requiring explicit passing of parameters through VI [[connector pane]] terminals. These are common issues in even small-sized programs.

Another common use is to encapsulate some functionality, especially functionality that is linked to persistent data or resources like files or devices. This encapsulation protects the resource and provides an extensible interface for interacting with the data or resource. The encapsulation also allows you to avoid a plethora of shift registers in a single VI. You can offload the shift-register to the Functional Global, and call it when needed, without worrying about wiring the data through all your case structures.

To get a better idea of what can be done with Functional Globals, here is a list of things that can be done:
*Load information from a file into a FG, access it anywhere in your program
*Maintain your system’s configuration parameters in one location.
*Store a control reference (like a tree control) in a FG, and then define an interface to manage that control. For complex controls like trees and multi-column listboxes this can simplify your top-level code.
*Timers are well implemented with FGs. You can keep the start time in the shift register, and then check the elapsed time when you call it again.
*Automatically preallocate an array when the FG is first called, then use “Replace Array Subset” to efficiently manipulate the array.
*Keep an ‘Undo’ list (stack) that allows you to push changes onto a stack, and pop them off when you need to undo the change.
The list could go on and on – whatever you can dream up!

==Race Conditions and Locking==
One of the main reasons that Functional Globals are encouraged in lieu of [[global variable]]s is race conditions. The majority of Functional Globals are, by definition, not reentrant so that different calls to the FG will all refer to the same shift registers and hence the same data or resource. This means that when a VI calls a FG, that FG is locked or reserved for use by the calling VI. Other VIs need to wait until it is done before they can call the FG.

Global variables are reentrant. If you try to write a value to the global in several places in your code, updates to the value are unpredictable with respect to time. This means that changes to the global can be subject to race conditions. This is especially true if you read/write to the global where a race condition could occur between the read and the write of the variable.

The downside for Functional Globals is that the locking that takes place can be a bottleneck in the code if many VIs are trying to access the FG at the same time. The majority of applications will not have a problem, but care must be taken if speed is a concern.

It is also important to note that Functional Globals are not a cure-all for race conditions. If actions on the Functional Global are not atomic (i.e. they require more than one call to the FG) then race conditions are still possible. Race conditions are only eliminated if all updates to the data are done inside the FG, in a single call. Here are a couple ways to still allow race conditions with FGs.
*Ask for the data from the FG, change it, and then write it back to the FG.
*Successive modifications, such as {Set data, normalize data, sort data, output max} By the time you sort the data, new data could have been set that hasn’t been normalized.

==Benefits==
#Efficient Memory Usage – Because the VI retains the same data space regardless of it use in the code, only a single call to the memory manager is made. If arrays are stored in the USR, and replace array element primitives used, then the memory space is efficiently used wherever the VI is called.
#Reduces problems with race conditions, as discussed above.
#Error checking can be done on data writes (Global variables don’t allow this).
#High-level code more readable – By moving shift registers and code logic into Functional Globals with readable action lists, top-level code become simpler and cleaner.
#Reuse. Many FGs are generic enough to be used over and over again.

==Concerns==
===Busy connector panes===
Terminals get used up quickly, so be sure to design well up front and choose a connector pane with more terminals than you need. You can avoid excessive terminal usage by grouping all of your data into a cluster (preferably, a [[Type Definition]]) that is passed in and out of your functional global which will allow you to bundle and unbundle specific variables as needed on your main VI.

===Data Persistence===
Data in a USR, and hence in a Functional Global, disappears if the owning VI goes out of memory. When a VI runs for the first time, all of its subVIs that are not already in memory are loaded into memory and they belong to that parent VI. If that parent VI is stopped, all of the subVIs that belong to it are also released from memory – even if there are other VIs in memory still referencing those subVIs. The next time one of those subVIs is run, it is loaded into memory again and that calling VI becomes the new parent VI. But if there was anything stored in USRs, that data is now gone.

This behavior is different from a queue reference, for instance, where the queue is only destroyed when ALL VIs referencing it leave memory. It means that if you use Functional Globals across multiple top-level VIs, then you need to have a VI that is run first and contains all of your Functional Globals as subVIs. This ‘First Run’ VI must stay in memory until all other top-level VIs are closed to insure that the Functional Global data will be available.

===Performance===
Some testing has shown that, as of LabVIEW 8.5, using a [[Case Structure]] performs better (from 1.5x to 3x) than a [[Select function]] for controlling the data flow of the Set/Write vs. the Get/Read operation.

==Reentrant functional globals==
===Unshared data===
There are certain problems where you do not need to share the persistent data elsewhere in the code. If you create a '''windowed average''' VI, it can be made reentrant and can be used in multiple places in your code to average data streams. This is an example of an in-place operation that is not shared, but requires persistent data. Timing a process in a single loop could be done with one instance of a Functional Global. Making this timing FG reentrant allows the developer to use that same timing FG to time other processes. See [[Reentrant VI]] for more information.

===By reference===
It’s possible to make use of reentrancy to duplicate functional globals. This allows to create as many globals as you need (even at run time) without duplicating code or modifying the original FG. The main disadvantage of this technique is the necessity to keep a reference to every instance of the functional global and pass them to the VIs or subVIs that will use them.

With this method, the only change to the original FG is to make the VI reentrant. Keep in mind that, from now on, this functional global can’t be used in the habitual way, since any instance will retain its own values.

To create an instance of the functional global, open it with the '''Open VI Reference''' function (use option 0x08 to prepare for reentrant run) and use the output reference to set the control values, run the VI and get the results. To facilitate things an avoid mistakes when getting/setting values, may be advisable to use the '''Call by Reference node'''. Furthermore, the encapsulation of the FG actions in specific wrappers, as detailed in the Structure section above, is also useful.

==See Also==
*[[Global variable]]
*[[State machine]]

==External Links==
*[http://forums.lavag.org/LV2OO-Style-Global-v20-from-NI-Week-presentation-t8780.html LAVA forum discussion about LV2OO-style globals]
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328 NI Forums Community Nugget on Action Engines]
*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

[[category:design patterns]]

Strict Type Definition

2008-01-02T18:01:15Z

Pbrooks100: Added image to clarify how to make a CTL a typdef

A strict type definition [STD] is like a [[Type Definition|type definition]] with well-defined appearance.

<center>[[Image:Type_Def_Status.png]]</center>

Well-defined appearance means that all instances of STD's share the appearance of that STD, e.g. their properties cannot be changed (except of label, caption and enable-state).

This is handy whenever the size, color etc. needs to be fixed. Think of sophisticated screen designs or stacked STDs. STDs are created by saving as this type of control - similar to 'simple' type definitions.

==See Also==
* [[Type Definition]]

==External Links==
* Creating Type Definitions and Strict Type Definitions[http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_type_defs/]

[[Category:user interface]]

Type Definition

2008-01-02T17:59:30Z

Pbrooks100: Added image to clarify how to make a CTL a typdef

A type definition [TD] is a custom control (CTL) file that has been marked as a type definition.

<center>[[Image:Type_Def_Status.png]]</center>

Instances of the TD are linked to their definition. You cannot edit functional properties of TD's instances, but only visual properties. To change functional properties you have to edit their TD. All changes in a TD are propagated to all of its instances, when you save the TD or choose to 'apply changes'.

Type definitions may be nested, i.e. may contain other TDs. You use this to define clusters of different data, which are defined as well and as such can be accessed on different levels. Review the properties of, say, a waveform chart, using a property node. You'll find a property 'Bounds' for the chart itself as well as for its caption, label, scales, even the scales' markers and so on.

==See Also==
* [[Strict Type Definition]]

==External Links==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_type_defs/ Creating Type Definitions and Strict Type Definitions]

[[category:user interface]]

File:Type Def Status.png

2008-01-02T17:52:58Z

Pbrooks100: Type Def. Status selector options.

Type Def. Status selector options.

Enumerated type

2008-01-02T17:30:04Z

Pbrooks100:

{{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 enum's. 

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

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

[[category:data types]]

Enumerated type

2008-01-02T17:29:35Z

Pbrooks100: /* 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 enum's. 

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

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

[[category:data types]]

Functional global variable

2008-01-02T12:07:38Z

Pbrooks100:

{{TOCnestright}}
Functional Globals are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals (FGs) most often make use of uninitialized shift registers (USRs). USRs are shift registers that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

==Alternative Nomenclature==
Functional Globals are known by various names among LabVIEW programmers.
*LV2 globals – because LV2 supported uninitialized shift registers
*USR globals – since most FGs make use of uninitialized shift registers
* VIG - "VI Global" as the VI performs the functionality of a global
*[[Action engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

==Structure==
The most common form of a Functional Global is a [[While Loop]] with a TRUE wired to the stop condition. This forces the loop to terminate after just one execution, meaning the while loop is only used to provide a place to put USRs. A [[For Loop]] could also be used with a constant wired to the count terminal. Another method is to use a single-element queue to store the data, though this requires more mouse clicks to implement. The performance of each of these is very close and most likely will vary a little from computer to computer.

[[Image:Simple_FG.PNG|frame|center|Simple Functional Global using a While Loop]]

In order to specify what action to perform, an [[enumerated type]] is often used as an input to the Functional Global. Other methods are possible (Booleans, First Call?, etc.), but an enumerated type provides for a readable, extensible list of actions. Furthermore, saving the enumerated type as a typedef control makes any changes to the list automatically update wherever the Functional Global is used in the code. The ‘action’ input is fed to a case structure which contains the code to implement for each of the defined actions.

For more complex situations, multiple actions can be performed on a single call to the FG. This can be a straightforward [[state machine]], or it can allow for different actions based on the data received or on the existence of resources, etc.

The data in a Functional Global could be of any type, but very often there will be several data elements in a single FG. It is helpful to group the data into a cluster to limit the number of wires entering and leaving the FG. Designing the data structures and how you cluster your data should be done early on, rather than haphazardly growing your clusters as you grow your program.

In order to deal with varying input requirements on the different actions, one can create ‘wrappers’ around the Functional Global that allow for different inputs to be required. This also gives the benefit of being able to search your code for certain actions as you can search for a specific VI, but not a specific enumerated type’s value.

==Uses==
The primary use of Functional Globals is to provide data sharing across an entire project, both horizontally and vertically. Horizontal sharing means multiple top-level VIs running autonomously can all have access to the same data. Vertical sharing means that subVIs at any depth will have access to the data without requiring explicit passing of parameters through VI [[connector pane]] terminals. These are common issues in even small-sized programs.

Another common use is to encapsulate some functionality, especially functionality that is linked to persistent data or resources like files or devices. This encapsulation protects the resource and provides an extensible interface for interacting with the data or resource. The encapsulation also allows you to avoid a plethora of shift registers in a single VI. You can offload the shift-register to the Functional Global, and call it when needed, without worrying about wiring the data through all your case structures.

To get a better idea of what can be done with Functional Globals, here is a list of things that can be done:
*Load information from a file into a FG, access it anywhere in your program
*Maintain your system’s configuration parameters in one location.
*Store a control reference (like a tree control) in a FG, and then define an interface to manage that control. For complex controls like trees and multi-column listboxes this can simplify your top-level code.
*Timers are well implemented with FGs. You can keep the start time in the shift register, and then check the elapsed time when you call it again.
*Automatically preallocate an array when the FG is first called, then use “Replace Array Subset” to efficiently manipulate the array.
*Keep an ‘Undo’ list (stack) that allows you to push changes onto a stack, and pop them off when you need to undo the change.
The list could go on and on – whatever you can dream up!

==Race Conditions and Locking==
One of the main reasons that Functional Globals are encouraged in lieu of [[global variable]]s is race conditions. The majority of Functional Globals are, by definition, not reentrant so that different calls to the FG will all refer to the same shift registers and hence the same data or resource. This means that when a VI calls a FG, that FG is locked or reserved for use by the calling VI. Other VIs need to wait until it is done before they can call the FG.

Global variables are reentrant. If you try to write a value to the global in several places in your code, updates to the value are unpredictable with respect to time. This means that changes to the global can be subject to race conditions. This is especially true if you read/write to the global where a race condition could occur between the read and the write of the variable.

The downside for Functional Globals is that the locking that takes place can be a bottleneck in the code if many VIs are trying to access the FG at the same time. The majority of applications will not have a problem, but care must be taken if speed is a concern.

It is also important to note that Functional Globals are not a cure-all for race conditions. If actions on the Functional Global are not atomic (i.e. they require more than one call to the FG) then race conditions are still possible. Race conditions are only eliminated if all updates to the data are done inside the FG, in a single call. Here are a couple ways to still allow race conditions with FGs.
*Ask for the data from the FG, change it, and then write it back to the FG.
*Successive modifications, such as {Set data, normalize data, sort data, output max} By the time you sort the data, new data could have been set that hasn’t been normalized.

==Benefits==
#Efficient Memory Usage – Because the VI retains the same data space regardless of it use in the code, only a single call to the memory manager is made. If arrays are stored in the USR, and replace array element primitives used, then the memory space is efficiently used wherever the VI is called.
#Reduces problems with race conditions, as discussed above.
#Error checking can be done on data writes (Global variables don’t allow this).
#High-level code more readable – By moving shift registers and code logic into Functional Globals with readable action lists, top-level code become simpler and cleaner.
#Reuse. Many FGs are generic enough to be used over and over again.

==Concerns==
===Busy connector panes===
Terminals get used up quickly, so be sure to design well up front and choose a connector pane with more terminals than you need. You can avoid excessive terminal usage by grouping all of your data into a cluster (preferably, a [[Type Definition]]) that is passed in and out of your functional global which will allow you to bundle and unbundle specific variables as needed on your main VI.

===Data Persistence===
Data in a USR, and hence in a Functional Global, disappears if the owning VI goes out of memory. When a VI runs for the first time, all of its subVIs that are not already in memory are loaded into memory and they belong to that parent VI. If that parent VI is stopped, all of the subVIs that belong to it are also released from memory – even if there are other VIs in memory still referencing those subVIs. The next time one of those subVIs is run, it is loaded into memory again and that calling VI becomes the new parent VI. But if there was anything stored in USRs, that data is now gone.

This behavior is different from a queue reference, for instance, where the queue is only destroyed when ALL VIs referencing it leave memory. It means that if you use Functional Globals across multiple top-level VIs, then you need to have a VI that is run first and contains all of your Functional Globals as subVIs. This ‘First Run’ VI must stay in memory until all other top-level VIs are closed to insure that the Functional Global data will be available.

===Performance===
Some testing has shown that, as of LabVIEW 8.5, using a [[Case Structure]] performs better (from 1.5x to 3x) than a [[Select function]] for controlling the data flow of the Set/Write vs. the Get/Read operation.

==Reentrant functional globals==
===Unshared data===
There are certain problems where you do not need to share the persistent data elsewhere in the code. If you create a '''windowed average''' VI, it can be made reentrant and can be used in multiple places in your code to average data streams. This is an example of an in-place operation that is not shared, but requires persistent data. Timing a process in a single loop could be done with one instance of a Functional Global. Making this timing FG reentrant allows the developer to use that same timing FG to time other processes. See [[Reentrant VI]] for more information.

===By reference===
It’s possible to make use of reentrancy to duplicate functional globals. This allows to create as many globals as you need (even at run time) without duplicating code or modifying the original FG. The main disadvantage of this technique is the necessity to keep a reference to every instance of the functional global and pass them to the VIs or subVIs that will use them.

With this method, the only change to the original FG is to make the VI reentrant. Keep in mind that, from now on, this functional global can’t be used in the habitual way, since any instance will retain its own values.

To create an instance of the functional global, open it with the '''Open VI Reference''' function (use option 0x08 to prepare for reentrant run) and use the output reference to set the control values, run the VI and get the results. To facilitate things an avoid mistakes when getting/setting values, may be advisable to use the '''Call by Reference node'''. Furthermore, the encapsulation of the FG actions in specific wrappers, as detailed in the Structure section above, is also useful.

==See Also==
*[[Global variable]]
*[[State machine]]

==External Links==
*[http://forums.lavag.org/LV2OO-Style-Global-v20-from-NI-Week-presentation-t8780.html LAVA forum discussion about LV2OO-style globals]
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328 NI Forums Community Nugget on Action Engines]
*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

[[category:design patterns]]

Functional global variable

2008-01-02T12:07:17Z

Pbrooks100:

{{TOCnestright}}
Functional Globals are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals (FGs) most often make use of uninitialized shift registers (USRs). USRs are shift registers that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

==Alternative Nomenclature==
Functional Globals are known by various names among LabVIEW programmers.
*LV2 globals – because LV2 supported uninitialized shift registers
*USR globals – since most FGs make use of uninitialized shift registers
* VIG - "VI Global" as the VI performs the functionality of a global
*[[Action Engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

==Structure==
The most common form of a Functional Global is a [[While Loop]] with a TRUE wired to the stop condition. This forces the loop to terminate after just one execution, meaning the while loop is only used to provide a place to put USRs. A [[For Loop]] could also be used with a constant wired to the count terminal. Another method is to use a single-element queue to store the data, though this requires more mouse clicks to implement. The performance of each of these is very close and most likely will vary a little from computer to computer.

[[Image:Simple_FG.PNG|frame|center|Simple Functional Global using a While Loop]]

In order to specify what action to perform, an [[enumerated type]] is often used as an input to the Functional Global. Other methods are possible (Booleans, First Call?, etc.), but an enumerated type provides for a readable, extensible list of actions. Furthermore, saving the enumerated type as a typedef control makes any changes to the list automatically update wherever the Functional Global is used in the code. The ‘action’ input is fed to a case structure which contains the code to implement for each of the defined actions.

For more complex situations, multiple actions can be performed on a single call to the FG. This can be a straightforward [[state machine]], or it can allow for different actions based on the data received or on the existence of resources, etc.

The data in a Functional Global could be of any type, but very often there will be several data elements in a single FG. It is helpful to group the data into a cluster to limit the number of wires entering and leaving the FG. Designing the data structures and how you cluster your data should be done early on, rather than haphazardly growing your clusters as you grow your program.

In order to deal with varying input requirements on the different actions, one can create ‘wrappers’ around the Functional Global that allow for different inputs to be required. This also gives the benefit of being able to search your code for certain actions as you can search for a specific VI, but not a specific enumerated type’s value.

==Uses==
The primary use of Functional Globals is to provide data sharing across an entire project, both horizontally and vertically. Horizontal sharing means multiple top-level VIs running autonomously can all have access to the same data. Vertical sharing means that subVIs at any depth will have access to the data without requiring explicit passing of parameters through VI [[connector pane]] terminals. These are common issues in even small-sized programs.

Another common use is to encapsulate some functionality, especially functionality that is linked to persistent data or resources like files or devices. This encapsulation protects the resource and provides an extensible interface for interacting with the data or resource. The encapsulation also allows you to avoid a plethora of shift registers in a single VI. You can offload the shift-register to the Functional Global, and call it when needed, without worrying about wiring the data through all your case structures.

To get a better idea of what can be done with Functional Globals, here is a list of things that can be done:
*Load information from a file into a FG, access it anywhere in your program
*Maintain your system’s configuration parameters in one location.
*Store a control reference (like a tree control) in a FG, and then define an interface to manage that control. For complex controls like trees and multi-column listboxes this can simplify your top-level code.
*Timers are well implemented with FGs. You can keep the start time in the shift register, and then check the elapsed time when you call it again.
*Automatically preallocate an array when the FG is first called, then use “Replace Array Subset” to efficiently manipulate the array.
*Keep an ‘Undo’ list (stack) that allows you to push changes onto a stack, and pop them off when you need to undo the change.
The list could go on and on – whatever you can dream up!

==Race Conditions and Locking==
One of the main reasons that Functional Globals are encouraged in lieu of [[global variable]]s is race conditions. The majority of Functional Globals are, by definition, not reentrant so that different calls to the FG will all refer to the same shift registers and hence the same data or resource. This means that when a VI calls a FG, that FG is locked or reserved for use by the calling VI. Other VIs need to wait until it is done before they can call the FG.

Global variables are reentrant. If you try to write a value to the global in several places in your code, updates to the value are unpredictable with respect to time. This means that changes to the global can be subject to race conditions. This is especially true if you read/write to the global where a race condition could occur between the read and the write of the variable.

The downside for Functional Globals is that the locking that takes place can be a bottleneck in the code if many VIs are trying to access the FG at the same time. The majority of applications will not have a problem, but care must be taken if speed is a concern.

It is also important to note that Functional Globals are not a cure-all for race conditions. If actions on the Functional Global are not atomic (i.e. they require more than one call to the FG) then race conditions are still possible. Race conditions are only eliminated if all updates to the data are done inside the FG, in a single call. Here are a couple ways to still allow race conditions with FGs.
*Ask for the data from the FG, change it, and then write it back to the FG.
*Successive modifications, such as {Set data, normalize data, sort data, output max} By the time you sort the data, new data could have been set that hasn’t been normalized.

==Benefits==
#Efficient Memory Usage – Because the VI retains the same data space regardless of it use in the code, only a single call to the memory manager is made. If arrays are stored in the USR, and replace array element primitives used, then the memory space is efficiently used wherever the VI is called.
#Reduces problems with race conditions, as discussed above.
#Error checking can be done on data writes (Global variables don’t allow this).
#High-level code more readable – By moving shift registers and code logic into Functional Globals with readable action lists, top-level code become simpler and cleaner.
#Reuse. Many FGs are generic enough to be used over and over again.

==Concerns==
===Busy connector panes===
Terminals get used up quickly, so be sure to design well up front and choose a connector pane with more terminals than you need. You can avoid excessive terminal usage by grouping all of your data into a cluster (preferably, a [[Type Definition]]) that is passed in and out of your functional global which will allow you to bundle and unbundle specific variables as needed on your main VI.

===Data Persistence===
Data in a USR, and hence in a Functional Global, disappears if the owning VI goes out of memory. When a VI runs for the first time, all of its subVIs that are not already in memory are loaded into memory and they belong to that parent VI. If that parent VI is stopped, all of the subVIs that belong to it are also released from memory – even if there are other VIs in memory still referencing those subVIs. The next time one of those subVIs is run, it is loaded into memory again and that calling VI becomes the new parent VI. But if there was anything stored in USRs, that data is now gone.

This behavior is different from a queue reference, for instance, where the queue is only destroyed when ALL VIs referencing it leave memory. It means that if you use Functional Globals across multiple top-level VIs, then you need to have a VI that is run first and contains all of your Functional Globals as subVIs. This ‘First Run’ VI must stay in memory until all other top-level VIs are closed to insure that the Functional Global data will be available.

===Performance===
Some testing has shown that, as of LabVIEW 8.5, using a [[Case Structure]] performs better (from 1.5x to 3x) than a [[Select function]] for controlling the data flow of the Set/Write vs. the Get/Read operation.

==Reentrant functional globals==
===Unshared data===
There are certain problems where you do not need to share the persistent data elsewhere in the code. If you create a '''windowed average''' VI, it can be made reentrant and can be used in multiple places in your code to average data streams. This is an example of an in-place operation that is not shared, but requires persistent data. Timing a process in a single loop could be done with one instance of a Functional Global. Making this timing FG reentrant allows the developer to use that same timing FG to time other processes. See [[Reentrant VI]] for more information.

===By reference===
It’s possible to make use of reentrancy to duplicate functional globals. This allows to create as many globals as you need (even at run time) without duplicating code or modifying the original FG. The main disadvantage of this technique is the necessity to keep a reference to every instance of the functional global and pass them to the VIs or subVIs that will use them.

With this method, the only change to the original FG is to make the VI reentrant. Keep in mind that, from now on, this functional global can’t be used in the habitual way, since any instance will retain its own values.

To create an instance of the functional global, open it with the '''Open VI Reference''' function (use option 0x08 to prepare for reentrant run) and use the output reference to set the control values, run the VI and get the results. To facilitate things an avoid mistakes when getting/setting values, may be advisable to use the '''Call by Reference node'''. Furthermore, the encapsulation of the FG actions in specific wrappers, as detailed in the Structure section above, is also useful.

==See Also==
*[[Global variable]]
*[[State machine]]

==External Links==
*[http://forums.lavag.org/LV2OO-Style-Global-v20-from-NI-Week-presentation-t8780.html LAVA forum discussion about LV2OO-style globals]
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328 NI Forums Community Nugget on Action Engines]
*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

[[category:design patterns]]

Functional global variable

2008-01-02T12:03:14Z

Pbrooks100:

{{TOCnestright}}
Functional Globals are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals (FGs) most often make use of uninitialized shift registers (USRs). USRs are shift registers that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

==Alternative Nomenclature==
Functional Globals are known by various names among LabVIEW programmers.
*LV2 globals – because LV2 supported uninitialized shift registers
*USR globals – since most FGs make use of uninitialized shift registers
* VIG - "VI Global" as the VI performs the functionality of a global
*[[Action engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

==Structure==
The most common form of a Functional Global is a [[While Loop]] with a TRUE wired to the stop condition. This forces the loop to terminate after just one execution, meaning the while loop is only used to provide a place to put USRs. A [[For Loop]] could also be used with a constant wired to the count terminal. Another method is to use a single-element queue to store the data, though this requires more mouse clicks to implement. The performance of each of these is very close and most likely will vary a little from computer to computer.

[[Image:Simple_FG.PNG|frame|center|Simple Functional Global using a While Loop]]

In order to specify what action to perform, an [[enumerated type]] is often used as an input to the Functional Global. Other methods are possible (Booleans, First Call?, etc.), but an enumerated type provides for a readable, extensible list of actions. Furthermore, saving the enumerated type as a typedef control makes any changes to the list automatically update wherever the Functional Global is used in the code. The ‘action’ input is fed to a case structure which contains the code to implement for each of the defined actions.

For more complex situations, multiple actions can be performed on a single call to the FG. This can be a straightforward [[state machine]], or it can allow for different actions based on the data received or on the existence of resources, etc.

The data in a Functional Global could be of any type, but very often there will be several data elements in a single FG. It is helpful to group the data into a cluster to limit the number of wires entering and leaving the FG. Designing the data structures and how you cluster your data should be done early on, rather than haphazardly growing your clusters as you grow your program.

In order to deal with varying input requirements on the different actions, one can create ‘wrappers’ around the Functional Global that allow for different inputs to be required. This also gives the benefit of being able to search your code for certain actions as you can search for a specific VI, but not a specific enumerated type’s value.

==Uses==
The primary use of Functional Globals is to provide data sharing across an entire project, both horizontally and vertically. Horizontal sharing means multiple top-level VIs running autonomously can all have access to the same data. Vertical sharing means that subVIs at any depth will have access to the data without requiring explicit passing of parameters through VI [[connector pane]] terminals. These are common issues in even small-sized programs.

Another common use is to encapsulate some functionality, especially functionality that is linked to persistent data or resources like files or devices. This encapsulation protects the resource and provides an extensible interface for interacting with the data or resource. The encapsulation also allows you to avoid a plethora of shift registers in a single VI. You can offload the shift-register to the Functional Global, and call it when needed, without worrying about wiring the data through all your case structures.

To get a better idea of what can be done with Functional Globals, here is a list of things that can be done:
*Load information from a file into a FG, access it anywhere in your program
*Maintain your system’s configuration parameters in one location.
*Store a control reference (like a tree control) in a FG, and then define an interface to manage that control. For complex controls like trees and multi-column listboxes this can simplify your top-level code.
*Timers are well implemented with FGs. You can keep the start time in the shift register, and then check the elapsed time when you call it again.
*Automatically preallocate an array when the FG is first called, then use “Replace Array Subset” to efficiently manipulate the array.
*Keep an ‘Undo’ list (stack) that allows you to push changes onto a stack, and pop them off when you need to undo the change.
The list could go on and on – whatever you can dream up!

==Race Conditions and Locking==
One of the main reasons that Functional Globals are encouraged in lieu of [[global variable]]s is race conditions. The majority of Functional Globals are, by definition, not reentrant so that different calls to the FG will all refer to the same shift registers and hence the same data or resource. This means that when a VI calls a FG, that FG is locked or reserved for use by the calling VI. Other VIs need to wait until it is done before they can call the FG.

Global variables are reentrant. If you try to write a value to the global in several places in your code, updates to the value are unpredictable with respect to time. This means that changes to the global can be subject to race conditions. This is especially true if you read/write to the global where a race condition could occur between the read and the write of the variable.

The downside for Functional Globals is that the locking that takes place can be a bottleneck in the code if many VIs are trying to access the FG at the same time. The majority of applications will not have a problem, but care must be taken if speed is a concern.

It is also important to note that Functional Globals are not a cure-all for race conditions. If actions on the Functional Global are not atomic (i.e. they require more than one call to the FG) then race conditions are still possible. Race conditions are only eliminated if all updates to the data are done inside the FG, in a single call. Here are a couple ways to still allow race conditions with FGs.
*Ask for the data from the FG, change it, and then write it back to the FG.
*Successive modifications, such as {Set data, normalize data, sort data, output max} By the time you sort the data, new data could have been set that hasn’t been normalized.

==Benefits==
#Efficient Memory Usage – Because the VI retains the same data space regardless of it use in the code, only a single call to the memory manager is made. If arrays are stored in the USR, and replace array element primitives used, then the memory space is efficiently used wherever the VI is called.
#Reduces problems with race conditions, as discussed above.
#Error checking can be done on data writes (Global variables don’t allow this).
#High-level code more readable – By moving shift registers and code logic into Functional Globals with readable action lists, top-level code become simpler and cleaner.
#Reuse. Many FGs are generic enough to be used over and over again.

==Concerns==
===Busy connector panes===
Terminals get used up quickly, so be sure to design well up front and choose a connector pane with more terminals than you need. You can avoid excessive terminal usage by grouping all of your data into a cluster (preferably, a [[Type Definition]]) that is passed in and out of your functional global which will allow you to bundle and unbundle specific variables as needed on your main VI.

===Data Persistence===
Data in a USR, and hence in a Functional Global, disappears if the owning VI goes out of memory. When a VI runs for the first time, all of its subVIs that are not already in memory are loaded into memory and they belong to that parent VI. If that parent VI is stopped, all of the subVIs that belong to it are also released from memory – even if there are other VIs in memory still referencing those subVIs. The next time one of those subVIs is run, it is loaded into memory again and that calling VI becomes the new parent VI. But if there was anything stored in USRs, that data is now gone.

This behavior is different from a queue reference, for instance, where the queue is only destroyed when ALL VIs referencing it leave memory. It means that if you use Functional Globals across multiple top-level VIs, then you need to have a VI that is run first and contains all of your Functional Globals as subVIs. This ‘First Run’ VI must stay in memory until all other top-level VIs are closed to insure that the Functional Global data will be available.

===Performance===
Some testing has shown that, as of LabVIEW 8.5, using a [[Case Structure]] performs better (from 1.5x to 3x) than a [[Select function]] for controlling the data flow of the Set/Write vs. the Get/Read operation.

==Reentrant functional globals==
===Unshared data===
There are certain problems where you do not need to share the persistent data elsewhere in the code. If you create a '''windowed average''' VI, it can be made reentrant and can be used in multiple places in your code to average data streams. This is an example of an in-place operation that is not shared, but requires persistent data. Timing a process in a single loop could be done with one instance of a Functional Global. Making this timing FG reentrant allows the developer to use that same timing FG to time other processes. See [[Reentrant VI]] for more information.

===By reference===
It’s possible to make use of reentrancy to duplicate functional globals. This allows to create as many globals as you need (even at run time) without duplicating code or modifying the original FG. The main disadvantage of this technique is the necessity to keep a reference to every instance of the functional global and pass them to the VIs or subVIs that will use them.

With this method, the only change to the original FG is to make the VI reentrant. Keep in mind that, from now on, this functional global can’t be used in the habitual way, since any instance will retain its own values.

To create an instance of the functional global, open it with the '''Open VI Reference''' function (use option 0x08 to prepare for reentrant run) and use the output reference to set the control values, run the VI and get the results. To facilitate things an avoid mistakes when getting/setting values, may be advisable to use the '''Call by Reference node'''. Furthermore, the encapsulation of the FG actions in specific wrappers, as detailed in the Structure section above, is also useful.

==See Also==
*[[Global variable]]
*[[State machine]]

==External Links==
*[http://forums.lavag.org/LV2OO-Style-Global-v20-from-NI-Week-presentation-t8780.html LAVA forum discussion about LV2OO-style globals]
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328 NI Forums Community Nugget on Action Engines]
*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

[[category:design patterns]]

Functional global variable

2008-01-02T12:02:50Z

Pbrooks100:

{{TOCnestright}}
Functional Globals are VIs that allow controlled access to data or resources, often allowing various actions to be performed. Functional Globals (FGs) most often make use of uninitialized shift registers (USRs). USRs are shift registers that do not have a wired input coming into the left side of the loop. A USR stores its data between successive runs of the VI as long as the VI remains in memory.

==Alternative Nomenclature==
Functional Globals are known by various names among LabVIEW programmers.
*LV2 globals – because LV2 supported uninitialized shift registers
*USR globals – since most FGs make use of uninitialized shift registers
* VIG - "VI Global" as the VI performs the functionality of a global
*[[Action Engine]]s – it has been argued [http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328] that the term Functional Globals should refer to VIs that just allow read/write access to data. Action Engines would refer to the larger set of VIs that allow some defined action on the data.

The official name for these constructs in NI literature is Functional Global Variable, and a [http://forums.lavag.org/index.php?showtopic=2469&st=0 survey] on LAVA indicated that Functional Globals is also the most popular choice.

==Structure==
The most common form of a Functional Global is a [[While Loop]] with a TRUE wired to the stop condition. This forces the loop to terminate after just one execution, meaning the while loop is only used to provide a place to put USRs. A [[For Loop]] could also be used with a constant wired to the count terminal. Another method is to use a single-element queue to store the data, though this requires more mouse clicks to implement. The performance of each of these is very close and most likely will vary a little from computer to computer.

[[Image:Simple_FG.PNG|frame|center|Simple Functional Global using a While Loop]]

In order to specify what action to perform, an [[enumerated type]] is often used as an input to the Functional Global. Other methods are possible (Booleans, First Call?, etc.), but an enumerated type provides for a readable, extensible list of actions. Furthermore, saving the enumerated type as a typedef control makes any changes to the list automatically update wherever the Functional Global is used in the code. The ‘action’ input is fed to a case structure which contains the code to implement for each of the defined actions.

For more complex situations, multiple actions can be performed on a single call to the FG. This can be a straightforward [[state machine]], or it can allow for different actions based on the data received or on the existence of resources, etc.

The data in a Functional Global could be of any type, but very often there will be several data elements in a single FG. It is helpful to group the data into a cluster to limit the number of wires entering and leaving the FG. Designing the data structures and how you cluster your data should be done early on, rather than haphazardly growing your clusters as you grow your program.

In order to deal with varying input requirements on the different actions, one can create ‘wrappers’ around the Functional Global that allow for different inputs to be required. This also gives the benefit of being able to search your code for certain actions as you can search for a specific VI, but not a specific enumerated type’s value.

==Uses==
The primary use of Functional Globals is to provide data sharing across an entire project, both horizontally and vertically. Horizontal sharing means multiple top-level VIs running autonomously can all have access to the same data. Vertical sharing means that subVIs at any depth will have access to the data without requiring explicit passing of parameters through VI [[connector pane]] terminals. These are common issues in even small-sized programs.

Another common use is to encapsulate some functionality, especially functionality that is linked to persistent data or resources like files or devices. This encapsulation protects the resource and provides an extensible interface for interacting with the data or resource. The encapsulation also allows you to avoid a plethora of shift registers in a single VI. You can offload the shift-register to the Functional Global, and call it when needed, without worrying about wiring the data through all your case structures.

To get a better idea of what can be done with Functional Globals, here is a list of things that can be done:
*Load information from a file into a FG, access it anywhere in your program
*Maintain your system’s configuration parameters in one location.
*Store a control reference (like a tree control) in a FG, and then define an interface to manage that control. For complex controls like trees and multi-column listboxes this can simplify your top-level code.
*Timers are well implemented with FGs. You can keep the start time in the shift register, and then check the elapsed time when you call it again.
*Automatically preallocate an array when the FG is first called, then use “Replace Array Subset” to efficiently manipulate the array.
*Keep an ‘Undo’ list (stack) that allows you to push changes onto a stack, and pop them off when you need to undo the change.
The list could go on and on – whatever you can dream up!

==Race Conditions and Locking==
One of the main reasons that Functional Globals are encouraged in lieu of [[global variable]]s is race conditions. The majority of Functional Globals are, by definition, not reentrant so that different calls to the FG will all refer to the same shift registers and hence the same data or resource. This means that when a VI calls a FG, that FG is locked or reserved for use by the calling VI. Other VIs need to wait until it is done before they can call the FG.

Global variables are reentrant. If you try to write a value to the global in several places in your code, updates to the value are unpredictable with respect to time. This means that changes to the global can be subject to race conditions. This is especially true if you read/write to the global where a race condition could occur between the read and the write of the variable.

The downside for Functional Globals is that the locking that takes place can be a bottleneck in the code if many VIs are trying to access the FG at the same time. The majority of applications will not have a problem, but care must be taken if speed is a concern.

It is also important to note that Functional Globals are not a cure-all for race conditions. If actions on the Functional Global are not atomic (i.e. they require more than one call to the FG) then race conditions are still possible. Race conditions are only eliminated if all updates to the data are done inside the FG, in a single call. Here are a couple ways to still allow race conditions with FGs.
*Ask for the data from the FG, change it, and then write it back to the FG.
*Successive modifications, such as {Set data, normalize data, sort data, output max} By the time you sort the data, new data could have been set that hasn’t been normalized.

==Benefits==
#Efficient Memory Usage – Because the VI retains the same data space regardless of it use in the code, only a single call to the memory manager is made. If arrays are stored in the USR, and replace array element primitives used, then the memory space is efficiently used wherever the VI is called.
#Reduces problems with race conditions, as discussed above.
#Error checking can be done on data writes (Global variables don’t allow this).
#High-level code more readable – By moving shift registers and code logic into Functional Globals with readable action lists, top-level code become simpler and cleaner.
#Reuse. Many FGs are generic enough to be used over and over again.

==Concerns==
===Busy connector panes===
Terminals get used up quickly, so be sure to design well up front and choose a connector pane with more terminals than you need. You can avoid excessive terminal usage by grouping all of your data into a cluster (preferably, a [[Type Definition]]) that is passed in and out of your functional global which will allow you to bundle and unbundle specific variables as needed on your main VI.

===Data Persistence===
Data in a USR, and hence in a Functional Global, disappears if the owning VI goes out of memory. When a VI runs for the first time, all of its subVIs that are not already in memory are loaded into memory and they belong to that parent VI. If that parent VI is stopped, all of the subVIs that belong to it are also released from memory – even if there are other VIs in memory still referencing those subVIs. The next time one of those subVIs is run, it is loaded into memory again and that calling VI becomes the new parent VI. But if there was anything stored in USRs, that data is now gone.

This behavior is different from a queue reference, for instance, where the queue is only destroyed when ALL VIs referencing it leave memory. It means that if you use Functional Globals across multiple top-level VIs, then you need to have a VI that is run first and contains all of your Functional Globals as subVIs. This ‘First Run’ VI must stay in memory until all other top-level VIs are closed to insure that the Functional Global data will be available.

===Performance===
Some testing has shown that, as of LabVIEW 8.5, using a [[Case Structure]] performs better (from 1.5x to 3x) than a [[Select function]] for controlling the data flow of the Set/Write vs. the Get/Read operation.

==Reentrant functional globals==
===Unshared data===
There are certain problems where you do not need to share the persistent data elsewhere in the code. If you create a '''windowed average''' VI, it can be made reentrant and can be used in multiple places in your code to average data streams. This is an example of an in-place operation that is not shared, but requires persistent data. Timing a process in a single loop could be done with one instance of a Functional Global. Making this timing FG reentrant allows the developer to use that same timing FG to time other processes. See [[Reentrant VI]] for more information.

===By reference===
It’s possible to make use of reentrancy to duplicate functional globals. This allows to create as many globals as you need (even at run time) without duplicating code or modifying the original FG. The main disadvantage of this technique is the necessity to keep a reference to every instance of the functional global and pass them to the VIs or subVIs that will use them.

With this method, the only change to the original FG is to make the VI reentrant. Keep in mind that, from now on, this functional global can’t be used in the habitual way, since any instance will retain its own values.

To create an instance of the functional global, open it with the '''Open VI Reference''' function (use option 0x08 to prepare for reentrant run) and use the output reference to set the control values, run the VI and get the results. To facilitate things an avoid mistakes when getting/setting values, may be advisable to use the '''Call by Reference node'''. Furthermore, the encapsulation of the FG actions in specific wrappers, as detailed in the Structure section above, is also useful.

==See Also==
*[[Global variable]]
*[[State machine]]

==External Links==
*[http://forums.lavag.org/LV2OO-Style-Global-v20-from-NI-Week-presentation-t8780.html LAVA forum discussion about LV2OO-style globals]
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=240328&query.id=618807#M240328 NI Forums Community Nugget on Action Engines]
*[http://zone.ni.com/reference/en-XX/help/371361A-01/lvconcepts/suggestions_for_exec/#Functional_Global_Variables NI Documentation on Functional Global Variables]

[[category:design patterns]]

Queued State Machine

2007-11-13T20:05:34Z

Pbrooks100: /* External Links */

{{stub}}
== See Also ==
* [[State Machine]]

[[category:design patterns]]

== External Links ==
[http://expressionflow.com/2007/10/01/labview-queued-state-machine-architecture/ LabVIEW Queued State Machine Architecture] - ExpressionFlow

Queued State Machine

2007-11-13T19:59:02Z

Pbrooks100: /* See Also */

{{stub}}
== See Also ==
* [[State Machine]]

[[category:design patterns]]

== External Links ==
[http://expressionflow.com/2007/10/01/labview-queued-state-machine-architecture/ LoabVIEW Queued State Machine Architecture] - ExpressionFlow

LabVIEW Technical Resource

2007-10-09T18:28:20Z

Pbrooks100: /* External links */

{{stub}}

LabVIEW Technical Resource (LTR) was a periodical print magazine that ran from 1993 to 2006.

[[LTR FAQ]]

== External links ==

* [http://forums.lavag.org/LTR-Magazine-t2562.html&pid=8897&mode=threaded#entry8897 LTR Magazine - Ending Publication] (LAVA Thread)

[[category:LabVIEW fundamentals]]
[[category:LabVIEW ecosystem]]
[[category:LabVIEW history]]

LabVIEW Technical Resource

2007-10-09T18:26:27Z

Pbrooks100:

{{stub}}

LabVIEW Technical Resource (LTR) was a periodical print magazine that ran from 1993 to 2006.

[[LTR FAQ]]

== External links ==

* [http://forums.lavag.org/LTR-Magazine-t2562.html&pid=8897&mode=threaded#entry8897 LTR Magazine] (LAVA Thread)

[[category:LabVIEW fundamentals]]
[[category:LabVIEW ecosystem]]
[[category:LabVIEW history]]

LabVIEW Technical Resource/FAQ

2007-10-09T16:04:59Z

Pbrooks100:

== The LTR domain name has expired and does not reference any LTR related information. The text below is from the README.TXT file included with each of the LTR Packs and is provided here as a reference to the licensing terms when LTR was actively available: ==

----

LTR LICENSING...
FREQUENTLY ASKED QUESTIONS

FAQ - Can I modify the VIs on the LTR CD for use in my LabVIEW application?

Yes. Our license states that as an LTR subscriber:

1. You are granted the permission to use or alter the LTR VIs in any manner you see fit, including the making of derivatives.
2. If you publish any derivative of any specific item of Technical Content included in this LTR Software, you must include any notice of copyright of the original LTR Author and of LTR Publishing, Inc. This is not a restriction, just a request to acknowledge the source of information. Basically this means you may not delete the LTR references contained in the Documentation area of the VI Properties.
3. This permission does not extend to wholesale copying or wholesale modification of the Technical Content in its entirety or large portions thereof. This means you may not take most or all of our products and resell them under another name, e.g. the LabVIEW Technical Report.

FAQ - If I use LTR VIs in my LabVIEW application, can I distribute the VIs in a commercial application?

LTR licensing policies have always permitted commercial distribution of LabVIEW applications that include original or modified LTR VIs, as long as the LTR references are included. We request in the LTR masthead (found on page 2 of each issue) that you notify LTR of commercial distribution as a courtesy to the contributing authors.

FAQ - Can I share LTR articles and disk material directly with my colleagues?

As with most purchased software, you may not burn multiple copies of the LTR CDs to distribute to others. A single user subscriber should not make photocopies or PDFs of LTR articles to distribute to others. Please refer interested colleagues to our website at ltrpub.com to view free sample issues and obtain order information. Group subscription discounts are also available to order online.

FAQ - Can I allow access to the LTR articles and VIs on my company server?

You are permitted to add LTR VIs that you have modified to your company code repository for use by others. You also can share your LabVIEW applications that include LTR VIs. Remember to keep the LTR references in the VI Properties.

However, you should not put LTR products, such as the searchable Library of Back Issues CD on your server for company-wide reference without purchasing the correct number of licenses. Multiple user licensing information is available at ltrpub.com/cd for the Library of Back Issues CD.

FAQ - I’d like to submit articles and VIs to LTR for publication. Do I retain the original copyright?

Yes, authors retain the copyright to their original work. LTR typically adds its own editorial content to both articles and disk material, and exercises editorial selection and control in creating compilations of various authors’ works into its publications. Consequently, LTR maintains copyright ownership and protection of its derivative and compilation works, while the authors retain the original copyright to their work. Authors sign a permission to publish agreement granting use of the material by subscribers under the LTR licensing agreement.

FAQ - Does the single-user license in the LTR license mean that I can use my LTR Products on more than one computer?

Yes. When an individual purchases an LTR product with a single-user license, permission is granted to use the LTR products on all computers used by that single individual.
------------------------------------------------

LICENSE AGREEMENT

This License Agreement sets forth the terms and conditions for licensing of the LTR Publishing, Inc. (“LTR”) computer program and documentation with which this License Agreement is included and any updates or maintenance releases thereto (the “LTR Software”). Installing and using the LTR Software indicates that you have read and understand this License Agreement and accept its terms and conditions. If you do not agree to all of the terms of this License Agreement, return this product for a full refund.

Overview

The purpose of this overview is to explain the licensing policies and procedures of LTR Publishing, Inc. contained in this License Agreement. LTR publishes technical articles and publishes source code and VIs ("Technical Content") in compilations and in stand_alone formats. LTR's articles and Technical Content are authored either directly by LTR or by a wide variety of individuals who submit their work to LTR for publication and use but retain the original copyright to their work ("LTR Authors"). In publishing the works of other authors, LTR typically adds its own editorial content to both articles and Technical Content, and exercises editorial selection and control in creating compilations of various authors' works into its publications. Consequently, LTR maintains copyright ownership and protection of its derivative and compilation works.

The goal of this License Agreement is to protect LTR's interest in compilations of articles and Technical Content while permitting purchasers of the LTR Software to make use of the information contained in the articles and Technical Content. As a result, LTR prohibits anyone from copying in whole or part individual articles, compilations of articles, and compilations of source code, but permits end_user licensees to copy and use individual Technical Content and to make emergency backups of LTR products.

License Grant and Restrictions

Single User Version. If you purchased a full, single_user version of the LTR Software, you are granted a limited non_exclusive license to use a copy of the enclosed LTR Software on the computer(s) used by a single individual. You may make one (1) backup copy of the LTR Software for your own use.

Multi User Version. If you purchased the multi_user version of the LTR Software, you are granted a limited non_exclusive license to: (i) use copies of the enclosed LTR Software on up to five (5) computer(s) used by up to a total of five (5) individuals (who are your owners, employees or contractors) on all such computers; and (ii) place a copy of your company's LTR Software data file on a network for use by up to five (5) individuals (who are your owners, employees or contractors). Additional user licensing packs are available for purchase from LTR Publishing, Inc.

Specific Items of Technical Content. If you purchased any version of the LTR Software, you are granted the permission to use or alter specific items of Technical Content in any manner you see fit, including the making of derivatives. This permission does not extend to wholesale copying or wholesale modification of the Technical Content in its entirety or large portions thereof. If you publish any derivative of any specific item of Technical Content included in this LTR Software, you must include a notice of copyright of the original LTR Author and of LTR Publishing, Inc.

General. The LTR Software is protected by the copyright laws of the United States of America and by international treaties. LTR Publishing, Inc. retains all right, title and interest in the LTR Software. Except for the Technical Content, you may not decompile, reverse engineer, disassemble, or otherwise reduce the LTR Software to human_perceivable form or disable any functionality which limits the use of the LTR Software. You may not translate, rent or sublicense (including offering the LTR Software to third parties on an applications service provider or time_sharing basis), assign, loan, resell for profit, or distribute the LTR Software, disk(s), or related materials. Except for the Technical Content, you may not create derivative works based upon the LTR Software or any part thereof. You may not network the LTR Software, except to the extent you have purchased license(s) for the multi_user version as referenced above.

Limited Warranty

If you are not 100% satisfied with this LTR Software, LTR Publishing, Inc.’s entire liability and your exclusive remedy shall be return of the LTR Software within ninety (90) days of purchase for a full refund If the media on which the LTR Software is published is defective, you may obtain replacement disks within ninety (90) days from date of purchase. To receive a refund or replacement, you must return the LTR Software to us or to an authorized Dealer or Distributor with a copy of your receipt.

Disclaimer of Warranties

EXCEPT AS PROVIDED ABOVE, THIS SOFTWARE AND ANY CONTENT ACCESSIBLE THROUGH THE SOFTWARE ARE PROVIDED "AS_IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LTR DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE, DISKS, RELATED MATERIALS AND ANY SUCH CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR QUALITY, THEIR SECURITY, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. LTR DOES NOT WARRANT THAT THE SOFTWARE OR ANY RELATED CONTENT IS FREE FROM BUGS, VIRUSES, ERRORS, OR OTHER PROGRAM LIMITATIONS. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSIONS MAY NOT APPLY TO YOU. IN THAT EVENT, ANY IMPLIED WARRANTIES ARE LIMITED IN DURATION TO NINETY (90) DAYS FROM THE DATE OF PURCHASE OF THE SOFTWARE. HOWEVER, SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY HAVE OTHER RIGHTS AS WELL, WHICH VARY FROM STATE TO STATE.

Limitation of Liability and Damages

THE ENTIRE LIABILITY OF LTR AND ITS REPRESENTATIVES (AS DEFINED BELOW) FOR ANY REASON SHALL BE LIMITED TO THE AMOUNT PAID BY THE CUSTOMER FOR THE SOFTWARE UNLESS OTHERWISE SEPARATELY AGREED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LTR AND ITS SUBSIDIARIES, AFFILIATES, LICENSORS, PARTICIPATING FINANCIAL INSTITUTIONS, LTR AUTHORS, THIRD_PARTY CONTENT PROVIDERS, DISTRIBUTORS, DEALERS OR SUPPLIERS ("REPRESENTATIVES") ARE NOT LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS OR INVESTMENT, OR THE LIKE), WHETHER BASED ON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF LTR OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME STATES DO NOT ALLOW THE LIMITATION AND/OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. THE LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN LTR AND YOU. LTR WOULD NOT BE ABLE TO HAVE PROVIDED THIS SOFTWARE WITHOUT SUCH LIMITATIONS.

Transfers

You may transfer all your rights to use the LTR Software to another person or legal entity provided you transfer this Agreement, the LTR Software, including all copies, update and prior versions to such person or entity and that you retain no copies, including copies stored on computer.

General Provisions

This Agreement sets forth LTR's and its Representatives' entire liability and your exclusive remedy with respect to the LTR Software. You acknowledge that this Agreement is a complete statement of the agreement between you and LTR with respect to the LTR Software, and that there are no other prior or contemporaneous understandings, promises, representations, or descriptions with respect to the LTR Software.

This Agreement shall govern any content related to the LTR Software, unless such content are subject to a separate written agreement between you and LTR or its Representatives. However, the limitations of liability and disclaimer of warranties in this Agreement shall apply to LTR and its Representatives with respect to such content except to the extent provided otherwise in a separate written agreement approved by LTR between you and LTR or the applicable Representative(s).

This Agreement does not limit any rights that LTR may have under trade secret, copyright, patent, or other laws. The Representatives of LTR are not authorized to make modifications to this Agreement, or to make any additional representations, commitments, or warranties binding on LTR, other than in writing signed by an officer of LTR. Accordingly, such additional statements are not binding on LTR and you should not rely upon such statements. If any provision of this Agreement is invalid or unenforceable under applicable law, then it is, to that extent, deemed omitted and the remaining provisions will continue in full force and effect. The validity and performance of this Agreement shall be governed by Texas law (without reference to choice of law principles), except as to copyright and trademark matters, which are covered by federal laws. This Agreement is deemed entered into at Plano, Collin County, Texas, and shall be construed as to its fair meaning and not strictly for or against either party. In the event of litigation between you and us concerning the LTR Software or Documentation, the venue of such litigation shall be in Collin County, Texas, and the prevailing party in the litigation will be entitled to recover attorney fees and expenses from the other party.

Termination

This Agreement may be terminated by LTR Publishing, Inc. immediately and without notice if you fail to comply with any term or condition of this Agreement. It will also automatically terminate if you fail to comply with any term or condition of this license agreement. Upon such termination, you must immediately return or destroy all complete and partial copies of the LTR Software, including all backup copies.

Amendments to License Agreement

From time to time, LTR Publishing, Inc. may change the terms and conditions of this Agreement. LTR Publishing, Inc. will notify you of any such change. For the latest version of this Agreement, go to www.ltrpub.com/license, or such other site designated by LTR. Your continued use of this LTR Software will indicate your agreement to the change.

U.S. Government Restricted Rights

This software is provided with restricted rights. Use, duplication, or disclosure by the government is subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer LTR Software clause at 48 CFR 252.227-7013, or in subparagraphs (a) through (d) of the Commercial Computer LTR Software Restricted Rights clause at 48 CFR 52.227-19, as applicable. The contractor/manufacturer is LTR Publishing, Inc., 860 Avenue F, Suite 100, Plano, Texas 75074.

Export Restrictions

You acknowledge and agree that the LTR Software is subject to restrictions and controls imposed by the Export Administration Act and the Export Administration Regulations ("Export Laws"). You will not export or re-export the LTR Software to any country, person or entity subject to U.S. export restrictions, including (a) any country to which the U.S. has embargoed or restricted the export of goods or services, which currently include, but are not necessarily limited to Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria, or to any national of any such country, wherever located, who intends to transmit or transport the LTR Software back to such country; (b) to any person or entity who you know or have reason to know will utilize the LTR Software in the design, development or production of nuclear, chemical or biological weapons; or (c) to any person or entity who has been prohibited from participating in U.S. export transactions by any federal agency of the U.S. government. You warrant and represent that neither the U.S. Commerce Department, Bureau of Export Administration nor any other U.S. federal agency has suspended, revoked or denied your export privileges.

LabVIEW™ is a registered trademark of National Instruments Corporation, Austin, Texas. Other parties’ trademarks or service marks are the property of their respective owners and should be treated as such.

Copyright (c) 2004 by LTR Publishing, Inc. All rights reserved.

LabVIEW Technical Resource/FAQ

2007-10-09T15:35:20Z

Pbrooks100:

LTR LICENSING...
FREQUENTLY ASKED QUESTIONS

FAQ - Can I modify the VIs on the LTR CD for use in my LabVIEW application?

Yes. Our license states that as an LTR subscriber:

1. You are granted the permission to use or alter the LTR VIs in any manner you see fit, including the making of derivatives.
2. If you publish any derivative of any specific item of Technical Content included in this LTR Software, you must include any notice of copyright of the original LTR Author and of LTR Publishing, Inc. This is not a restriction, just a request to acknowledge the source of information. Basically this means you may not delete the LTR references contained in the Documentation area of the VI Properties.
3. This permission does not extend to wholesale copying or wholesale modification of the Technical Content in its entirety or large portions thereof. This means you may not take most or all of our products and resell them under another name, e.g. the LabVIEW Technical Report.

FAQ - If I use LTR VIs in my LabVIEW application, can I distribute the VIs in a commercial application?

LTR licensing policies have always permitted commercial distribution of LabVIEW applications that include original or modified LTR VIs, as long as the LTR references are included. We request in the LTR masthead (found on page 2 of each issue) that you notify LTR of commercial distribution as a courtesy to the contributing authors.

FAQ - Can I share LTR articles and disk material directly with my colleagues?

As with most purchased software, you may not burn multiple copies of the LTR CDs to distribute to others. A single user subscriber should not make photocopies or PDFs of LTR articles to distribute to others. Please refer interested colleagues to our website at ltrpub.com to view free sample issues and obtain order information. Group subscription discounts are also available to order online.

FAQ - Can I allow access to the LTR articles and VIs on my company server?

You are permitted to add LTR VIs that you have modified to your company code repository for use by others. You also can share your LabVIEW applications that include LTR VIs. Remember to keep the LTR references in the VI Properties.

However, you should not put LTR products, such as the searchable Library of Back Issues CD on your server for company-wide reference without purchasing the correct number of licenses. Multiple user licensing information is available at ltrpub.com/cd for the Library of Back Issues CD.

FAQ - I’d like to submit articles and VIs to LTR for publication. Do I retain the original copyright?

Yes, authors retain the copyright to their original work. LTR typically adds its own editorial content to both articles and disk material, and exercises editorial selection and control in creating compilations of various authors’ works into its publications. Consequently, LTR maintains copyright ownership and protection of its derivative and compilation works, while the authors retain the original copyright to their work. Authors sign a permission to publish agreement granting use of the material by subscribers under the LTR licensing agreement.

FAQ - Does the single-user license in the LTR license mean that I can use my LTR Products on more than one computer?

Yes. When an individual purchases an LTR product with a single-user license, permission is granted to use the LTR products on all computers used by that single individual.
------------------------------------------------

LICENSE AGREEMENT

This License Agreement sets forth the terms and conditions for licensing of the LTR Publishing, Inc. (“LTR”) computer program and documentation with which this License Agreement is included and any updates or maintenance releases thereto (the “LTR Software”). Installing and using the LTR Software indicates that you have read and understand this License Agreement and accept its terms and conditions. If you do not agree to all of the terms of this License Agreement, return this product for a full refund.

Overview

The purpose of this overview is to explain the licensing policies and procedures of LTR Publishing, Inc. contained in this License Agreement. LTR publishes technical articles and publishes source code and VIs ("Technical Content") in compilations and in stand_alone formats. LTR's articles and Technical Content are authored either directly by LTR or by a wide variety of individuals who submit their work to LTR for publication and use but retain the original copyright to their work ("LTR Authors"). In publishing the works of other authors, LTR typically adds its own editorial content to both articles and Technical Content, and exercises editorial selection and control in creating compilations of various authors' works into its publications. Consequently, LTR maintains copyright ownership and protection of its derivative and compilation works.

The goal of this License Agreement is to protect LTR's interest in compilations of articles and Technical Content while permitting purchasers of the LTR Software to make use of the information contained in the articles and Technical Content. As a result, LTR prohibits anyone from copying in whole or part individual articles, compilations of articles, and compilations of source code, but permits end_user licensees to copy and use individual Technical Content and to make emergency backups of LTR products.

License Grant and Restrictions

Single User Version. If you purchased a full, single_user version of the LTR Software, you are granted a limited non_exclusive license to use a copy of the enclosed LTR Software on the computer(s) used by a single individual. You may make one (1) backup copy of the LTR Software for your own use.

Multi User Version. If you purchased the multi_user version of the LTR Software, you are granted a limited non_exclusive license to: (i) use copies of the enclosed LTR Software on up to five (5) computer(s) used by up to a total of five (5) individuals (who are your owners, employees or contractors) on all such computers; and (ii) place a copy of your company's LTR Software data file on a network for use by up to five (5) individuals (who are your owners, employees or contractors). Additional user licensing packs are available for purchase from LTR Publishing, Inc.

Specific Items of Technical Content. If you purchased any version of the LTR Software, you are granted the permission to use or alter specific items of Technical Content in any manner you see fit, including the making of derivatives. This permission does not extend to wholesale copying or wholesale modification of the Technical Content in its entirety or large portions thereof. If you publish any derivative of any specific item of Technical Content included in this LTR Software, you must include a notice of copyright of the original LTR Author and of LTR Publishing, Inc.

General. The LTR Software is protected by the copyright laws of the United States of America and by international treaties. LTR Publishing, Inc. retains all right, title and interest in the LTR Software. Except for the Technical Content, you may not decompile, reverse engineer, disassemble, or otherwise reduce the LTR Software to human_perceivable form or disable any functionality which limits the use of the LTR Software. You may not translate, rent or sublicense (including offering the LTR Software to third parties on an applications service provider or time_sharing basis), assign, loan, resell for profit, or distribute the LTR Software, disk(s), or related materials. Except for the Technical Content, you may not create derivative works based upon the LTR Software or any part thereof. You may not network the LTR Software, except to the extent you have purchased license(s) for the multi_user version as referenced above.

Limited Warranty

If you are not 100% satisfied with this LTR Software, LTR Publishing, Inc.’s entire liability and your exclusive remedy shall be return of the LTR Software within ninety (90) days of purchase for a full refund If the media on which the LTR Software is published is defective, you may obtain replacement disks within ninety (90) days from date of purchase. To receive a refund or replacement, you must return the LTR Software to us or to an authorized Dealer or Distributor with a copy of your receipt.

Disclaimer of Warranties

EXCEPT AS PROVIDED ABOVE, THIS SOFTWARE AND ANY CONTENT ACCESSIBLE THROUGH THE SOFTWARE ARE PROVIDED "AS_IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LTR DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE, DISKS, RELATED MATERIALS AND ANY SUCH CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR QUALITY, THEIR SECURITY, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. LTR DOES NOT WARRANT THAT THE SOFTWARE OR ANY RELATED CONTENT IS FREE FROM BUGS, VIRUSES, ERRORS, OR OTHER PROGRAM LIMITATIONS. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSIONS MAY NOT APPLY TO YOU. IN THAT EVENT, ANY IMPLIED WARRANTIES ARE LIMITED IN DURATION TO NINETY (90) DAYS FROM THE DATE OF PURCHASE OF THE SOFTWARE. HOWEVER, SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY HAVE OTHER RIGHTS AS WELL, WHICH VARY FROM STATE TO STATE.

Limitation of Liability and Damages

THE ENTIRE LIABILITY OF LTR AND ITS REPRESENTATIVES (AS DEFINED BELOW) FOR ANY REASON SHALL BE LIMITED TO THE AMOUNT PAID BY THE CUSTOMER FOR THE SOFTWARE UNLESS OTHERWISE SEPARATELY AGREED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LTR AND ITS SUBSIDIARIES, AFFILIATES, LICENSORS, PARTICIPATING FINANCIAL INSTITUTIONS, LTR AUTHORS, THIRD_PARTY CONTENT PROVIDERS, DISTRIBUTORS, DEALERS OR SUPPLIERS ("REPRESENTATIVES") ARE NOT LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS OR INVESTMENT, OR THE LIKE), WHETHER BASED ON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF LTR OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME STATES DO NOT ALLOW THE LIMITATION AND/OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. THE LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN LTR AND YOU. LTR WOULD NOT BE ABLE TO HAVE PROVIDED THIS SOFTWARE WITHOUT SUCH LIMITATIONS.

Transfers

You may transfer all your rights to use the LTR Software to another person or legal entity provided you transfer this Agreement, the LTR Software, including all copies, update and prior versions to such person or entity and that you retain no copies, including copies stored on computer.

General Provisions

This Agreement sets forth LTR's and its Representatives' entire liability and your exclusive remedy with respect to the LTR Software. You acknowledge that this Agreement is a complete statement of the agreement between you and LTR with respect to the LTR Software, and that there are no other prior or contemporaneous understandings, promises, representations, or descriptions with respect to the LTR Software.

This Agreement shall govern any content related to the LTR Software, unless such content are subject to a separate written agreement between you and LTR or its Representatives. However, the limitations of liability and disclaimer of warranties in this Agreement shall apply to LTR and its Representatives with respect to such content except to the extent provided otherwise in a separate written agreement approved by LTR between you and LTR or the applicable Representative(s).

This Agreement does not limit any rights that LTR may have under trade secret, copyright, patent, or other laws. The Representatives of LTR are not authorized to make modifications to this Agreement, or to make any additional representations, commitments, or warranties binding on LTR, other than in writing signed by an officer of LTR. Accordingly, such additional statements are not binding on LTR and you should not rely upon such statements. If any provision of this Agreement is invalid or unenforceable under applicable law, then it is, to that extent, deemed omitted and the remaining provisions will continue in full force and effect. The validity and performance of this Agreement shall be governed by Texas law (without reference to choice of law principles), except as to copyright and trademark matters, which are covered by federal laws. This Agreement is deemed entered into at Plano, Collin County, Texas, and shall be construed as to its fair meaning and not strictly for or against either party. In the event of litigation between you and us concerning the LTR Software or Documentation, the venue of such litigation shall be in Collin County, Texas, and the prevailing party in the litigation will be entitled to recover attorney fees and expenses from the other party.

Termination

This Agreement may be terminated by LTR Publishing, Inc. immediately and without notice if you fail to comply with any term or condition of this Agreement. It will also automatically terminate if you fail to comply with any term or condition of this license agreement. Upon such termination, you must immediately return or destroy all complete and partial copies of the LTR Software, including all backup copies.

Amendments to License Agreement

From time to time, LTR Publishing, Inc. may change the terms and conditions of this Agreement. LTR Publishing, Inc. will notify you of any such change. For the latest version of this Agreement, go to www.ltrpub.com/license, or such other site designated by LTR. Your continued use of this LTR Software will indicate your agreement to the change.

U.S. Government Restricted Rights

This software is provided with restricted rights. Use, duplication, or disclosure by the government is subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer LTR Software clause at 48 CFR 252.227-7013, or in subparagraphs (a) through (d) of the Commercial Computer LTR Software Restricted Rights clause at 48 CFR 52.227-19, as applicable. The contractor/manufacturer is LTR Publishing, Inc., 860 Avenue F, Suite 100, Plano, Texas 75074.

Export Restrictions

You acknowledge and agree that the LTR Software is subject to restrictions and controls imposed by the Export Administration Act and the Export Administration Regulations ("Export Laws"). You will not export or re-export the LTR Software to any country, person or entity subject to U.S. export restrictions, including (a) any country to which the U.S. has embargoed or restricted the export of goods or services, which currently include, but are not necessarily limited to Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria, or to any national of any such country, wherever located, who intends to transmit or transport the LTR Software back to such country; (b) to any person or entity who you know or have reason to know will utilize the LTR Software in the design, development or production of nuclear, chemical or biological weapons; or (c) to any person or entity who has been prohibited from participating in U.S. export transactions by any federal agency of the U.S. government. You warrant and represent that neither the U.S. Commerce Department, Bureau of Export Administration nor any other U.S. federal agency has suspended, revoked or denied your export privileges.

LabVIEW™ is a registered trademark of National Instruments Corporation, Austin, Texas. Other parties’ trademarks or service marks are the property of their respective owners and should be treated as such.

Copyright (c) 2004 by LTR Publishing, Inc. All rights reserved.

LabVIEW Technical Resource/FAQ

2007-10-09T15:34:26Z

Pbrooks100:

<blockquote>
LTR LICENSING...
FREQUENTLY ASKED QUESTIONS

FAQ - Can I modify the VIs on the LTR CD for use in my LabVIEW application?

Yes. Our license states that as an LTR subscriber:

1. You are granted the permission to use or alter the LTR VIs in any manner you see fit, including the making of derivatives.
2. If you publish any derivative of any specific item of Technical Content included in this LTR Software, you must include any notice of copyright of the original LTR Author and of LTR Publishing, Inc. This is not a restriction, just a request to acknowledge the source of information. Basically this means you may not delete the LTR references contained in the Documentation area of the VI Properties.
3. This permission does not extend to wholesale copying or wholesale modification of the Technical Content in its entirety or large portions thereof. This means you may not take most or all of our products and resell them under another name, e.g. the LabVIEW Technical Report.

FAQ - If I use LTR VIs in my LabVIEW application, can I distribute the VIs in a commercial application?

LTR licensing policies have always permitted commercial distribution of LabVIEW applications that include original or modified LTR VIs, as long as the LTR references are included. We request in the LTR masthead (found on page 2 of each issue) that you notify LTR of commercial distribution as a courtesy to the contributing authors.

FAQ - Can I share LTR articles and disk material directly with my colleagues?

As with most purchased software, you may not burn multiple copies of the LTR CDs to distribute to others. A single user subscriber should not make photocopies or PDFs of LTR articles to distribute to others. Please refer interested colleagues to our website at ltrpub.com to view free sample issues and obtain order information. Group subscription discounts are also available to order online.

FAQ - Can I allow access to the LTR articles and VIs on my company server?

You are permitted to add LTR VIs that you have modified to your company code repository for use by others. You also can share your LabVIEW applications that include LTR VIs. Remember to keep the LTR references in the VI Properties.

However, you should not put LTR products, such as the searchable Library of Back Issues CD on your server for company-wide reference without purchasing the correct number of licenses. Multiple user licensing information is available at ltrpub.com/cd for the Library of Back Issues CD.

FAQ - I’d like to submit articles and VIs to LTR for publication. Do I retain the original copyright?

Yes, authors retain the copyright to their original work. LTR typically adds its own editorial content to both articles and disk material, and exercises editorial selection and control in creating compilations of various authors’ works into its publications. Consequently, LTR maintains copyright ownership and protection of its derivative and compilation works, while the authors retain the original copyright to their work. Authors sign a permission to publish agreement granting use of the material by subscribers under the LTR licensing agreement.

FAQ - Does the single-user license in the LTR license mean that I can use my LTR Products on more than one computer?

Yes. When an individual purchases an LTR product with a single-user license, permission is granted to use the LTR products on all computers used by that single individual.
------------------------------------------------

LICENSE AGREEMENT

This License Agreement sets forth the terms and conditions for licensing of the LTR Publishing, Inc. (“LTR”) computer program and documentation with which this License Agreement is included and any updates or maintenance releases thereto (the “LTR Software”). Installing and using the LTR Software indicates that you have read and understand this License Agreement and accept its terms and conditions. If you do not agree to all of the terms of this License Agreement, return this product for a full refund.

Overview

The purpose of this overview is to explain the licensing policies and procedures of LTR Publishing, Inc. contained in this License Agreement. LTR publishes technical articles and publishes source code and VIs ("Technical Content") in compilations and in stand_alone formats. LTR's articles and Technical Content are authored either directly by LTR or by a wide variety of individuals who submit their work to LTR for publication and use but retain the original copyright to their work ("LTR Authors"). In publishing the works of other authors, LTR typically adds its own editorial content to both articles and Technical Content, and exercises editorial selection and control in creating compilations of various authors' works into its publications. Consequently, LTR maintains copyright ownership and protection of its derivative and compilation works.

The goal of this License Agreement is to protect LTR's interest in compilations of articles and Technical Content while permitting purchasers of the LTR Software to make use of the information contained in the articles and Technical Content. As a result, LTR prohibits anyone from copying in whole or part individual articles, compilations of articles, and compilations of source code, but permits end_user licensees to copy and use individual Technical Content and to make emergency backups of LTR products.

License Grant and Restrictions

Single User Version. If you purchased a full, single_user version of the LTR Software, you are granted a limited non_exclusive license to use a copy of the enclosed LTR Software on the computer(s) used by a single individual. You may make one (1) backup copy of the LTR Software for your own use.

Multi User Version. If you purchased the multi_user version of the LTR Software, you are granted a limited non_exclusive license to: (i) use copies of the enclosed LTR Software on up to five (5) computer(s) used by up to a total of five (5) individuals (who are your owners, employees or contractors) on all such computers; and (ii) place a copy of your company's LTR Software data file on a network for use by up to five (5) individuals (who are your owners, employees or contractors). Additional user licensing packs are available for purchase from LTR Publishing, Inc.

Specific Items of Technical Content. If you purchased any version of the LTR Software, you are granted the permission to use or alter specific items of Technical Content in any manner you see fit, including the making of derivatives. This permission does not extend to wholesale copying or wholesale modification of the Technical Content in its entirety or large portions thereof. If you publish any derivative of any specific item of Technical Content included in this LTR Software, you must include a notice of copyright of the original LTR Author and of LTR Publishing, Inc.

General. The LTR Software is protected by the copyright laws of the United States of America and by international treaties. LTR Publishing, Inc. retains all right, title and interest in the LTR Software. Except for the Technical Content, you may not decompile, reverse engineer, disassemble, or otherwise reduce the LTR Software to human_perceivable form or disable any functionality which limits the use of the LTR Software. You may not translate, rent or sublicense (including offering the LTR Software to third parties on an applications service provider or time_sharing basis), assign, loan, resell for profit, or distribute the LTR Software, disk(s), or related materials. Except for the Technical Content, you may not create derivative works based upon the LTR Software or any part thereof. You may not network the LTR Software, except to the extent you have purchased license(s) for the multi_user version as referenced above.

Limited Warranty

If you are not 100% satisfied with this LTR Software, LTR Publishing, Inc.’s entire liability and your exclusive remedy shall be return of the LTR Software within ninety (90) days of purchase for a full refund If the media on which the LTR Software is published is defective, you may obtain replacement disks within ninety (90) days from date of purchase. To receive a refund or replacement, you must return the LTR Software to us or to an authorized Dealer or Distributor with a copy of your receipt.

Disclaimer of Warranties

EXCEPT AS PROVIDED ABOVE, THIS SOFTWARE AND ANY CONTENT ACCESSIBLE THROUGH THE SOFTWARE ARE PROVIDED "AS_IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LTR DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE, DISKS, RELATED MATERIALS AND ANY SUCH CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR QUALITY, THEIR SECURITY, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. LTR DOES NOT WARRANT THAT THE SOFTWARE OR ANY RELATED CONTENT IS FREE FROM BUGS, VIRUSES, ERRORS, OR OTHER PROGRAM LIMITATIONS. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSIONS MAY NOT APPLY TO YOU. IN THAT EVENT, ANY IMPLIED WARRANTIES ARE LIMITED IN DURATION TO NINETY (90) DAYS FROM THE DATE OF PURCHASE OF THE SOFTWARE. HOWEVER, SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY HAVE OTHER RIGHTS AS WELL, WHICH VARY FROM STATE TO STATE.

Limitation of Liability and Damages

THE ENTIRE LIABILITY OF LTR AND ITS REPRESENTATIVES (AS DEFINED BELOW) FOR ANY REASON SHALL BE LIMITED TO THE AMOUNT PAID BY THE CUSTOMER FOR THE SOFTWARE UNLESS OTHERWISE SEPARATELY AGREED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LTR AND ITS SUBSIDIARIES, AFFILIATES, LICENSORS, PARTICIPATING FINANCIAL INSTITUTIONS, LTR AUTHORS, THIRD_PARTY CONTENT PROVIDERS, DISTRIBUTORS, DEALERS OR SUPPLIERS ("REPRESENTATIVES") ARE NOT LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS OR INVESTMENT, OR THE LIKE), WHETHER BASED ON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF LTR OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. SOME STATES DO NOT ALLOW THE LIMITATION AND/OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. THE LIMITATIONS OF DAMAGES SET FORTH ABOVE ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN LTR AND YOU. LTR WOULD NOT BE ABLE TO HAVE PROVIDED THIS SOFTWARE WITHOUT SUCH LIMITATIONS.

Transfers

You may transfer all your rights to use the LTR Software to another person or legal entity provided you transfer this Agreement, the LTR Software, including all copies, update and prior versions to such person or entity and that you retain no copies, including copies stored on computer.

General Provisions

This Agreement sets forth LTR's and its Representatives' entire liability and your exclusive remedy with respect to the LTR Software. You acknowledge that this Agreement is a complete statement of the agreement between you and LTR with respect to the LTR Software, and that there are no other prior or contemporaneous understandings, promises, representations, or descriptions with respect to the LTR Software.

This Agreement shall govern any content related to the LTR Software, unless such content are subject to a separate written agreement between you and LTR or its Representatives. However, the limitations of liability and disclaimer of warranties in this Agreement shall apply to LTR and its Representatives with respect to such content except to the extent provided otherwise in a separate written agreement approved by LTR between you and LTR or the applicable Representative(s).

This Agreement does not limit any rights that LTR may have under trade secret, copyright, patent, or other laws. The Representatives of LTR are not authorized to make modifications to this Agreement, or to make any additional representations, commitments, or warranties binding on LTR, other than in writing signed by an officer of LTR. Accordingly, such additional statements are not binding on LTR and you should not rely upon such statements. If any provision of this Agreement is invalid or unenforceable under applicable law, then it is, to that extent, deemed omitted and the remaining provisions will continue in full force and effect. The validity and performance of this Agreement shall be governed by Texas law (without reference to choice of law principles), except as to copyright and trademark matters, which are covered by federal laws. This Agreement is deemed entered into at Plano, Collin County, Texas, and shall be construed as to its fair meaning and not strictly for or against either party. In the event of litigation between you and us concerning the LTR Software or Documentation, the venue of such litigation shall be in Collin County, Texas, and the prevailing party in the litigation will be entitled to recover attorney fees and expenses from the other party.

Termination

This Agreement may be terminated by LTR Publishing, Inc. immediately and without notice if you fail to comply with any term or condition of this Agreement. It will also automatically terminate if you fail to comply with any term or condition of this license agreement. Upon such termination, you must immediately return or destroy all complete and partial copies of the LTR Software, including all backup copies.

Amendments to License Agreement

From time to time, LTR Publishing, Inc. may change the terms and conditions of this Agreement. LTR Publishing, Inc. will notify you of any such change. For the latest version of this Agreement, go to www.ltrpub.com/license, or such other site designated by LTR. Your continued use of this LTR Software will indicate your agreement to the change.

U.S. Government Restricted Rights

This software is provided with restricted rights. Use, duplication, or disclosure by the government is subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer LTR Software clause at 48 CFR 252.227-7013, or in subparagraphs (a) through (d) of the Commercial Computer LTR Software Restricted Rights clause at 48 CFR 52.227-19, as applicable. The contractor/manufacturer is LTR Publishing, Inc., 860 Avenue F, Suite 100, Plano, Texas 75074.

Export Restrictions

You acknowledge and agree that the LTR Software is subject to restrictions and controls imposed by the Export Administration Act and the Export Administration Regulations ("Export Laws"). You will not export or re-export the LTR Software to any country, person or entity subject to U.S. export restrictions, including (a) any country to which the U.S. has embargoed or restricted the export of goods or services, which currently include, but are not necessarily limited to Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria, or to any national of any such country, wherever located, who intends to transmit or transport the LTR Software back to such country; (b) to any person or entity who you know or have reason to know will utilize the LTR Software in the design, development or production of nuclear, chemical or biological weapons; or (c) to any person or entity who has been prohibited from participating in U.S. export transactions by any federal agency of the U.S. government. You warrant and represent that neither the U.S. Commerce Department, Bureau of Export Administration nor any other U.S. federal agency has suspended, revoked or denied your export privileges.

LabVIEW™ is a registered trademark of National Instruments Corporation, Austin, Texas. Other parties’ trademarks or service marks are the property of their respective owners and should be treated as such.

Copyright (c) 2004 by LTR Publishing, Inc. All rights reserved.

</blockquote>

LabVIEW Technical Resource

2007-10-09T15:33:15Z

Pbrooks100:

{{stub}}

LabVIEW Technical Resource (LTR) was a periodical print magazine that ran from 1993 to 2006.

[[LTR FAQ]]
[[category:LabVIEW ecosystem]]
[[category:LabVIEW history]]

LabVIEW Technical Resource/FAQ

2007-10-09T15:32:34Z

Pbrooks100: New page: LTR LICENSING... FREQUENTLY ASKED QUESTIONS FAQ - Can I modify the VIs on the LTR CD for use in my LabVIEW application? Yes. Our license states that as an LTR subscriber: 1. You are gr...

Enumerated type

2007-08-22T10:22:24Z

Pbrooks100: /* Reccomendations */

== Enumerated Type (Enum) ==
Located under the Ring & Enum palette, a LabView enumerated type is used to associate a '''sequential''' numerical value to a programmer defined string
{| class="wikitable"
|-
[[Image:Enum_Palette_Location_LV_7.1_and_below.png]]
|}

== 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]] 
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 enum's. 

[[Image:Enum_properties_page.png‎ ]]

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

Enumerated type

2007-08-21T17:18:22Z

Pbrooks100:

== Enumerated Type (Enum) ==
Located under the Ring & Enum palette, a LabView enumerated type is used to associate a '''sequential''' numerical value to a programmer defined string
{| class="wikitable"
|-
[[Image:Enum_Palette_Location_LV_7.1_and_below.png]]
|}

== 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]] 
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.

== Reccomendations ==
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 enum's. 

[[Image:Enum_properties_page.png‎ ]]

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