This is the discussion topic for the wiki article: Insane Objects

Nice article Mike

I did a pretty major edit on the second section about using Heap Peek to delete the insane objects.

In the section where we talk about adding the configuration token, it would be good to link to a WIKI page about LabVIEW config files -- something that describes where to find the config file and the file name on each of the development platforms (Mac, Linux, Windows) and how to set config for built applications on each of the runtime platforms (Mac, Linux, Windows, Pharlap, PDA). I don't know enough to write that document.

I'd still really like to see an updated LabVIEW.ini list here on LAVA - there's a few excellent sites already, but they're either outdated or platform-specific.

Side note to Brian Renken: would it be okay with you if we mirrored and expanded on your LabVIEW.ini details in a wiki over here at LAVA? We've discussed it before here - what do you think?

Thank you for that but I was not the original author, I just added it and did some edits. It was originally brought over from the LabVIEW FAQ. I will take this opportunity to set some rules: Even though it is nice to acknowledge articles with a compliment, this is not appropriate here and is not helpfull. These article discussion threads should be only for real suggestions or criticisms for how to improve or further expand the article or topic. I'm more motivated by seeing others get inspired by my contributions and adding their own text or articles.


I noticed you added a non-existent wikilink. This is the best way to signal to other authors that a potential article is required or missing. Others looking to write an article can use these hints. There are already two articles:

LabVIEW ini File, LabVIEW ini Settings

Perhaps these can be refactored somehow. I think we need a master document. What should it be named? LabVIEW Configuration?

Ya, I think a new user edited Wiki document is better since these setting evolve between each version. Brian is very busy that I don't think his site will be updated any time in the future. I can contact him and ask.

Thanks Mike - I think it's an important resource that we could make even better

It definitely should not be anything with "ini" in the file name since the files on both Mac and Linux do not have a .ini file extension. In the shipping LabVIEW documentation he strings in the files are "configuration tokens" or "config tokens" and the files themselves are configuration files. I *think* that somewhere in the shipping docs is all this info and maybe it just needs to be cut/pasted into LAVA Wiki somewhere. .... actually, come to think of it ... maybe we should update the Wiki help to describe a way to link directly to the LabVIEW shipping documentation. All of it is uploaded on ni.com -- direct links to that stuff would occassionally be useful.

Here's the link for the English version of the online help:
http://zone.ni.com/reference/en-XX/help/371361B-01/
I'll ask tech docs if there's a more memorable URL.

And here's the link specific to LabVIEW config file:
http://zone.ni.com/reference/en-XX/help/37..._labview_prefs/

I asked Brian Renken if we could use the ini file content from his website and add it to the LabVIEW Wiki. My email:

His Response:


I think we should move forward on this.



Linking to external resources is ok and how to do it is explained in Help:Links . They should be collected at the end of the article under an External Resources section. I still need to compile a Wiki style guide which will outline this among other things. An external link however should only be there as a resource where someone can find more information, but it should not be used as the only source of information. The LabVIEW Wiki will not become a links site. Each article should evolve into a self sustaining document linking only to other LabVIEW Wiki articles for clarification.


If you can get approval from NI for LAVA to use NI copyrighted documentation material, that would be great... . Of course I could just do it and tell NI that Aristos Queue said it was ok. Aristos who?

That's awesome - a big thanks to Brian!

I think we should arrange the keys by version of LabVIEW - I'll start on a page this week sometime (unless someone else wants to take the lead on this?)

That's an excellent idea! I've got another idea just as good... let me look up your LabVIEW serial number and put a bit of code into saving a VI that says
if (serialnumber==xyz) {
MoveWireEndpoints1PixelRandomDir();
}

Seriously though, I hadn't thought about the copyright issue. What does the shrink wrap license say about sharing the documentation of LV?