Pet Peeves

[Ben]

Another peev of mine is hypocrasy. See this thread on LAVA

http://forums.lavag.org/LEDarray-t7082.html&st=0

Ben,

Shut up and do some coding!

Message Edited by Ben on 03-28-2007 07:57 AM

[altenbach]

---

@tst wrote:

...

Yes, but what about the white wires?

For those who don't know them, the white wires are a little known feature of LV. They are used to carry all the background data LV needs to perform its work and basically hold the diagram together. You can sometimes see them if you color your diagram in a different color and run with execution highlighting.

---

Demo VIs with all controls at default (empty arrays, zeroes, etc.). VIs should have some typical default data so we don't have to guess what the inputs should contain.

---

That's simply easy to forget.

---

Yes, the "white wires". Actually, they are not really white, but magically adapt to any current background color. 😉 They also carry data from locals(write) to locals(read).

Loading data into controls is not only easy to forget, beginners also don't really know how to do that. Tha't why we need a nice article "guidelines for posting code" that would explain it in a sentence or two.

Back to the peeves:

• Posting a small demo VI but attaching it as a 5MB application distribution, containing all VI.lib VIs used in the project.
• Posting a gigantic llb with hundreds of VIs with no word on what the toplevel is.
• Attaching an image as a bmp. or as an oversized image containing huge areas of white space.
• linking to an image that resides on the posters HD, nobody will ever see it.
• Posting a gigantic VI with hundreds of controls and indicators with the only words "It does not work".
• Posting a huge diagram without pointing out which of the 20 stacked sequence frames contains the problem code.

[tbd]

#1138 Posting a huge diagram without pointing out which of the 20 nearly identical stacked sequence frames...

#1139 This isn't a pet-peeve, really - more of a one time issue.  One time I opened a VI that must have been "doctored" because nothing appeared to happen yet it seems to have changed at least one registry-setting, loaded a key-logger, and installed a malicious-fish screen-saver that made my real pet fish swallow its tongue - then the fish-tank exploded, the house caught on fire, I died, etc...

Message Edited by tbd on 03-29-2007 10:59 PM

[Ray.R]

Altenbach missed this one:

this link

I thought he was gonna loose it.. 😉

[altenbach]

• Modifying a VI, then posting it under the same VI name as the original VI attachment in the original post.

Now anyone needs to save whatever is opened first under a new name, simply to be able to quickly view both versions side-by-side.

(http://forums.ni.com/ni/board/message?board.id=170&message.id=260015#M260015)

[MRedRaider]

• Using LabVIEW daily for a few years now and still missing the obvious.

[johnsold]

Posting a VI containing lots of DAQ VIs (or other hardware related stuff) when the question has to do with analysis of data. This is obviously related to the posting with default data peeve.

Posters who, after receiving the same answer from a Knight and several Zealous and Enthusiastic Veterans, ask again why their original program still does not work.

Lynn

p.s., I agree with Ray Farmer that the posting page should ask for LV versions, especially on attached VIs.

[PhillipBrooks]

Why should it be necessary to tell the forum what version the VI is? Couldn't the VI's header be read by the forum and the text added automatically? The forums already add date/time notes to my posts when I edit them...

Like the one below...

Message Edited by Phillip Brooks on 07-20-2007 09:01 AM

[mcduff]

1. Reviving old zombie threads 🙂
2. Threads with single word titles like LabVIEW, DAQ, Help Please!!!
3. Long threads where the OP asks multiple questions, sometimes changing questions, and gives no kudos.
4. Attachments with the following extensions: tar, 7z, doc, docx, ppt, pptx
5. Private messages asking for help
6. Asking questions such as "can my DAQ sample at XX", when a quick look at the specs would give the answer.
7. Questions like "I am new to LabVIEW and have been tasked to write facial recognition software/voice recognition software etc." Does anybody know where to start?

mcduff

[wiebe@CARYA]

---

@mcduff wrote:

1. Reviving old zombie threads 🙂
2. Threads with single word titles like LabVIEW, DAQ, Help Please!!!
3. Long threads where the OP asks multiple questions, sometimes changing questions, and gives no kudos.
4. Attachments with the following extensions: tar, 7z, doc, docx, ppt, pptx
5. Private messages asking for help
6. Asking questions such as "can my DAQ sample at XX", when a quick look at the specs would give the answer.
7. Questions like "I am new to LabVIEW and have been tasked to write facial recognition software/voice recognition software etc." Does anybody know where to start?

mcduff

---

8. Attaching images. Insert an image and\or attach a VI. *Sigh*

9. The "LMGTFY" question. Similar to 6., the first hit on Google is the answer.

10. Starting a new thread with the same question.