This is the discussion topic for the wiki article: http://wiki.lavag.org/LabVIEW_configuration_file

I looked at the Easter Egg tokens. There are a few missing...

ICantBelieveItsNotButter=0x12345678 (works in LV6 and 6.1 only)
ILuvLV20=TRUE (works in LV8.2 only)

And one other...
(which has actually been posted in various locations so I expect it to show up soon, but I'm not giving away all the toys...)

Thanks Stephen (I'm glad you went to the most important section first )

I recently contacted Scott Hannahs of Info-LabVIEW fame about his LabVIEW Options page:




Firstly: thank you so much Scott for allowing us to migrate his comprehensive list of LabVIEW Configuration File settings across to the LAVA wiki!

Secondly: anyone got some time to do even a small part of the migrations? There's a lot there, and if we all chip in then it should take no time

How do you want to do this? If you know where it goes, put it in the right category, otherwise "unknown"? If you know what it does or is, explain it, else leave explanation blank? Or try it out ... ? How do you want to divide it out?

I think the first thing to do would be identify which ones are already in the wiki, and once you've confirmed that each of their details are correct (eg: whcih versions of LabVIEW support it) scratch it off the list.

The settings are currently loosley categorised on the wiki under which page they appear on in the LabVIEW tools>options menu item (if they appear there at all). This is a very loose restriction, so you don't need to keep to it: just choose what you think is the most appropriate category and shove it in there.

For things that you don't know, just put "Unkown". There's templates for a number of settings sorted by their datatypes here - as it's a wiki, if a datatype doesn't exist, I encourage you to create one and put a copy of it on the templates page.

The first thing then, is to create a huge list from Scott's site that can be checked against the wiki listings. Then the resultant list of unlisted list items could be divided out into reasonable chunks to add to the wiki. I will work on creating such a list, and will upload it to this discussion.

Just a couple of comments: Is it really necessary to color the datatype text? Frankly, I find it distracting (Blue text; it's a link. Oh, no it's not.) Also, is it a good idea to make the "operating system" values little icons? Yes, they're cute, but again, they decrease readability. I know I have to squint to really make out the Sun logo.

I just noticed that clicking on the Discussion button creates a thread in this forum, even if you don't actually create a post. Sorry for the clutter.

I agree on the datatype text coloring; it is unnecessary since the format is so readable anyway. The only reason that coloring would be helpful would be if you were scanning for keys by datatype -- highly unlikely. I will take the color off of the ones I am modifying (which is practically all of them, right now).

I kinda like the OS glyphs. It doesn't take long to figure out what the icons mean, and after that I think it actually enhances the readability.

Actually, there are ways in the wiki to create real templates. See here. This simplifies repetative tasks and makes editing easier. This allows us to change the formatting of the entries later at any time. I'll create one for this.

Like I said, this becomes easier when a template is created
That's ok. If there's no response within a certain time to the post the thread gets deleted automatically.

I suggest you all wait until I make a template before we get too far ahead.

It's not necessary - just like it's not necessary to have wires and control/indicator nodes of different colors (try programming in black and white ) Efficient learning and retention is based on three key components:

• Emphasis
• Repitition
• Sense stimuli

The colored datatypes are an effort to use the third key component: sense stimuli. If I had the time, I'd replace them with icons like shown below so your brain will recognise them much more quickly than having to read and interpret the text:

== autoWireMax ==
Example: autoWireMax=24
Description: Maximum distance between nodes for autowiring to be active
Datatype:
Permitted Values: 1 to 2³²
Default Value: 16
LabVIEW Versions: 6.x, 7.x, 8.x
...


That's kind of the point: most of our brains work in images much more efficiently than text, so now that your brain knows the logo, it will be able to recognise it much more quikly: you won't have to squint again - your brain learned it, and knows what it means now.

All that aside, the beauty of the wiki is that if you feel strongly about it, go ahead and edit it.