labview ini keys overview

[GerdW]

A note from an NI-AE made me think: Why is there no list of LabVIEW ini file keys available, provided by the maker of the software?

So I propose the idea(s):

- NI should make a list of ini file keys with their usage. They may hide the "most secret" parts, but should keep the list up-to-date. There also should be given the LabVIEW version the key works on...

- NI could provide an INI file editor for the LabVIEW.ini file, similar to opening the page "about:config" in MozillaFirefox. The could even pop up the warning like FireFox does when opening that page...

[GerdW]

With "most secret" I speak of keys used just for NI-internal development purposes and similar. I understand NI will not provide them in a public list.

But: The key provided in the linked discussion surely doesn't fall into that category as it seems to be very stable when recommended by an AppNote...

I know the LabVIEW Options dialog is an editor for the LabVIEW.ini file. But it only edits a (small) subset of the available keys!

There are other ideas that address "advanced users and their comfort". Why not have an option to enable editing the "more hidden" keys when someone enables the "advanced user" options/settings also requested by other ideas?

Btw. I can edit comments, but I'm not able to edit my own idea entry?

[altenbach]

Btw. I can edit comments, but I'm not able to edit my own idea entry?

You should be able to edit your own idea within a certain timeframe. Note however that right after posting you are on a page where several ideas are listed. You now first need to click on your idea title to go back to a page where the edit option is available under "idea option" in the upper left..

[PaulG.]

The Options and LV.ini file need some serious upgrades. There are way too many "undocumented" features that affect the LV environment. Connector pane, for example. Why do I need to memorize an obscure command that I might need only once (if that) per year? Make it part of Options.

[AristosQueue (NI)]

All parts of the config file that we intend for you to edit are editable through the LabVIEW user interface. Any other parts are things that should be edited only when advised by tech support as a workaround to a problem. The file is human readable as this makes it easy to copy settings from one LV to another, but it is not intended as a document that is regularly user modified. It is, in fact, the equivalent of serialization of private data of an object, which should not be generally changed outside of the public interface of the class -- in this case, the metaphorical equivalent is the UI of LabVIEW. If there is a particular token that you know of that you would like to have as part of the UI, that's a separate idea.

[AristosQueue (NI)]

> Btw. I can edit comments, but I'm not able to edit my own idea entry?

We had some problems with people posting an idea, getting lots of kudos, then changing it to a different idea. So you only have a few minutes to make edits to an idea after you post it. After that, post a message to the moderator (click on "Idea Options" >> "Report To Moderator") asking the moderator to make the edits for you.