LabVIEW configuration file: Difference between revisions
Pjm_labview (talk | contribs) m New page: == LabVIEW Documentation Config File Settings == Some great resources already exists for cataloging the various keys used by ./labview.ini . In an effort not to duplicate the work that... |
Pjm_labview (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
== LabVIEW Documentation Config File Settings == | == LabVIEW Documentation Config File Settings == | ||
Some great resources already exists for cataloging the various keys used by ./labview.ini . In an effort not to duplicate the work that went into these resources we will merely provide a link to them here: | Some great resources already exists for cataloging the various keys used by ./labview.ini . In an effort not to duplicate the work that went into these resources we will merely provide a link to them here: | ||
| Line 16: | Line 14: | ||
* http://labview.brianrenken.com/INI/ | * http://labview.brianrenken.com/INI/ | ||
=== Some More Undocumented Keys === | |||
[code]BldApp.RemovePolyVIsandTypedefs=False[/code] | |||
[ | |||
BldApp.RemovePolyVIsandTypedefs=False | |||
By default, LV7 AppBuilder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. If some VI in your exe calls a VI outside (that was not planned by AppBuilder) and uses a type definition in order to pass parameters, you will meet such kind of problem for sure. This undocumented ini setting disables this new feature. | By default, LV7 AppBuilder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. If some VI in your exe calls a VI outside (that was not planned by AppBuilder) and uses a type definition in order to pass parameters, you will meet such kind of problem for sure. This undocumented ini setting disables this new feature. | ||
[code]coerceFromVariant=TRUE[/code] | |||
coerceFromVariant=TRUE | |||
This will cause Variants to automatically coerce to any data type. But be careful, there is no error handling. I wouldn't use this in your applications, but it is interesting. | This will cause Variants to automatically coerce to any data type. But be careful, there is no error handling. I wouldn't use this in your applications, but it is interesting. | ||
[code]structuresFadeToDiagramBeneath=TRUE[/code] | |||
structuresFadeToDiagramBeneath=TRUE | |||
Makes the diagram of structures semitransparent so that you can see objects hidden behind them. | Makes the diagram of structures semitransparent so that you can see objects hidden behind them. | ||
[code]suppressFileDlgForMissingVIs=TRUE[ode] | |||
suppressFileDlgForMissingVIs=TRUE | |||
Suppresses the file dialog for missing VIs. | Suppresses the file dialog for missing VIs. | ||
Revision as of 06:16, 17 March 2007
LabVIEW Documentation Config File Settings
Some great resources already exists for cataloging the various keys used by ./labview.ini . In an effort not to duplicate the work that went into these resources we will merely provide a link to them here:
LabVIEW Options on Scott Hannahs's LabVIEW Info Page:
- Version 7.0
- Version 6.1.0
- Version 6.0.2
- Version 5.1.1
And a listing of the undocumented one's on Brian Reneken's Website:
Some More Undocumented Keys
[code]BldApp.RemovePolyVIsandTypedefs=False[/code]
By default, LV7 AppBuilder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. If some VI in your exe calls a VI outside (that was not planned by AppBuilder) and uses a type definition in order to pass parameters, you will meet such kind of problem for sure. This undocumented ini setting disables this new feature.
[code]coerceFromVariant=TRUE[/code]
This will cause Variants to automatically coerce to any data type. But be careful, there is no error handling. I wouldn't use this in your applications, but it is interesting.
[code]structuresFadeToDiagramBeneath=TRUE[/code]
Makes the diagram of structures semitransparent so that you can see objects hidden behind them.
[code]suppressFileDlgForMissingVIs=TRUE[ode]
Suppresses the file dialog for missing VIs.