Jump to content

LabVIEW configuration file

From LabVIEW Wiki
Revision as of 06:14, 17 March 2007 by Pjm_labview (talk | contribs) (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...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

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.



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.



structuresFadeToDiagramBeneath=TRUE

Makes the diagram of structures semitransparent so that you can see objects hidden behind them.



suppressFileDlgForMissingVIs=TRUE

Suppresses the file dialog for missing VIs.