LabVIEW configuration file/Miscellaneous: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 21: | Line 21: | ||
LabVIEW Versions: 7.x<br/> | LabVIEW Versions: 7.x<br/> | ||
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/> | OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]]<br/> | ||
Notes: By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. | Notes: By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page. | ||
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears. | |||
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.<br/> | |||
== cleanupVisa == | == cleanupVisa == |
Revision as of 11:14, 18 May 2007
Template:LabVIEW configuration back This is a list of Miscellaneous LabVIEW ini File settings.
MRUFolders
Example | MRUFolders=TRUE
|
---|---|
Description | MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog. |
Datatype | Boolean |
Permitted Values | TRUE, FALSE |
Default Value | FALSE |
LabVIEW Versions | |
OS's Supported | |
Notes |
BldApp.RemovePolyVIsandTypedefs
Example: BldApp.RemovePolyVIsandTypedefs=FALSE
Description: Setting this to TRUE
stops the LabVIEW Application Builder from agressively removing polymorphic VIs and typedefs that it thinks are not required
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: TRUE
LabVIEW Versions: 7.x
OS's Supported:
Notes: By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on.
cleanupVisa
Example: coerceFromVariant=TRUE
Description: Force variants to automatically coerce to any data type that they are connected to
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 7.x, 8.x
OS's Supported:
Notes: Tread carefully, as using this function removes coercion notifivation, and does not useerror handling
cleanupVisa
Example: cleanupVisa=TRUE
Description: Automatically close VISA sessions - do not require the use of the VISA Close VI
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
dropThroughClicks
Example: dropThroughClicks=FALSE
Description: Allow drop-through clicks
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: TRUE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
ExternalNodesEnabled
Example: ExternalNodesEnabled=FALSE
Description: Enables use of External Nodes
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: 6.x?, 7.x: TRUE
8.x: FALSE
?
LabVIEW Versions: 6.x?, 7.x, 8.x
OS's Supported:
Notes: None
ExternalNodeDebugging
Example: ExternalNodeDebugging=FALSE
Description: Shows External Nodes for what they are: sequence diagrams
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 7.x, 8.x
OS's Supported:
Notes: None
hotMenus
Example: hotMenus=FALSE
Description: Use hot menus
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: TRUE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
openInRun
Example: openInRun=TRUE
Description: When opening VIs in the development environment, open them in run mode
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
readOnlyLock
Example: readOnlyLock=TRUE
Description: Treat read-only VIs as locked
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: It is important to set this to TRUE
when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited
showBDConstName
Example: showBDConstName=TRUE
Description: Show auto-constant labels
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
ShowTipStrings
Example: ShowTipStrings=FALSE
Description: Display Tip Strips during execution
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: TRUE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
Example: skipNavigatorDialog=TRUE
Description: Skip the navigation dialog on development environment launch
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
suppressFileDlgForMissingVIs
Example: suppressFileDlgForMissingVIs=TRUE
Description: Suppresses the file dialog for when loading a VI that has missing SubVIs
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
useNativeFileDialog
Example: useNativeFileDialog=FALSE
Description: Use the OS native file dialogs
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: TRUE
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x
OS's Supported:
Notes: None
XNodeWizardMode
Example: XNodeWizardMode=FALSE
Description: Allows contextual menus on XNodes to facilitate debugging
Datatype: Boolean
Permitted Values: TRUE
or FALSE
Default Value: FALSE
LabVIEW Versions: 8.x
OS's Supported:
Notes: None