Jump to content

LabVIEW configuration file: Difference between revisions

From LabVIEW Wiki
(No difference)

Revision as of 06:39, 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:

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[/code]

Suppresses the file dialog for missing VIs.