LabVIEW configuration file: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
This is a relatively comprehensive list of the settings that can be included in a LabIEW.ini file (or a compiled executable's ini file). Whilst some of these settings appera in the files by default, others may only appear when the features used require them to be there, whilst others still can only be added manually to provide access to backdoor settings and operations. | |||
LabVIEW ini Settings are organised into the following categories (in alphabetical order): | |||
# [[LabVIEW_ini_File.Block_Diagram|Block Diagram]] | |||
# [[LabVIEW_ini_File.Colors|Colors]] | |||
# [[LabVIEW_ini_File.Debugging|Debugging]] | |||
# [[LabVIEW_ini_File.Fonts|Fonts]] | |||
# [[LabVIEW_ini_File.Front_Panel|Front Panel]] | |||
# [[LabVIEW_ini_File.History|History]] | |||
# [[LabVIEW_ini_File.Miscellaneous|Miscellaneous]] | |||
# [[LabVIEW_ini_File.Paths|Paths]] | |||
# [[LabVIEW_ini_File.Performance|Performance]] | |||
# [[LabVIEW_ini_File.Printing|Printing]] | |||
# [[LabVIEW_ini_File.Time_and_Date|Time and Date]] | |||
# [[LabVIEW_ini_File.VI_Server|VI Server]] | |||
# [[LabVIEW_ini_File.Web_Server|Web Server]] | |||
---- | |||
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 13: | Line 32: | ||
=== Some More Undocumented Keys === | === Some More Undocumented Keys === | ||
[code]BldApp.RemovePolyVIsandTypedefs=False[/code] | [code]BldApp.RemovePolyVIsandTypedefs=False[/code] | ||
Revision as of 04:20, 5 May 2007
This is a relatively comprehensive list of the settings that can be included in a LabIEW.ini file (or a compiled executable's ini file). Whilst some of these settings appera in the files by default, others may only appear when the features used require them to be there, whilst others still can only be added manually to provide access to backdoor settings and operations.
LabVIEW ini Settings are organised into the following categories (in alphabetical order):
- Block Diagram
- Colors
- Debugging
- Fonts
- Front Panel
- History
- Miscellaneous
- Paths
- Performance
- Printing
- Time and Date
- VI Server
- Web Server
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 ones 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. Be warned on big VIs this will slow down you development environment.
[code]suppressFileDlgForMissingVIs=TRUE[/code]
Suppresses the file dialog for missing VIs.
Should I play with the undocumented ini keys?
The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow National Instruments a backdoor or a workaround for when the LabVIEW development team changes a behavior. They are also used to turn on obscure development features that the developers use to make or debug LabVIEW. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful.
The LabVIEW developers have never tried to hide any of these strings, but it is unlikely that you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth.
Even Greg McKaskle would not know what some of the settings do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that is needed for development, but not useful to even advanced LabVIEW users unless they have a death-wish.
If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LabVIEW left it. Don't ask tech support to fix it or complain that the LabVIEW attic has rusty nails and splinters.
Resedit is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LabVIEW.
Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preferences dialog.