Pet Peeves

[altenbach]

Browsing the forum we will always come across code where something is weird. Maybe this thread collection will help formulate some VI posting guidelines in the future.

Here are some of my pet peeves, I'm sure you have some too.

I don't like:

1. VIs that are set to "run when opened"
2. Front panels that are saved with the window "maximized to screen"
3. Block diagrams that are ... (see above).
4. VIs that contain spaces in the filename, because they will be replaced by "%20" during download.
5. Block diagrams with non-white background color. (no matter what you pick, one wire type will be camouflaged ;))
6. 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.
7. ...

For points 2 and 3, it seems everybody maximizes everything lately and I am wondering if I am in the minority. 😮 I always work on multiple VIs at the same time and need to see several diagrams at once (plus the web browser, the graphics program, the word processor, etc.). I feel cramped with the window maximised. Maybe others work better in "tunnel vision" mode, where nothing else can distract from the single VI diagram under investigation. 😉 What do you prefer?

[tbob]

My pet peeve is when someone posts a vi and he/she doesn't mention what version it is in.  I usually use LV 7.1.1, and when I try to open an LV 8.x vi, I get the warning message.  Then I have to close LV 7.1.1 and open LV 8.2.

But hold on, I have just installed Labview Version Chooser, see http://www.dataact.com/LVC.htm.  It recognizes what version the vi is written in and gives you the chance to open it in that version.  Pretty good stuff.

Also, I have a dual monitor system, so I can place vi's all over the place.  Makes it much easier to copy and paste from one vi to another.  I never need to maximize.  I share that pet peeve with Altenbach.  It is worth the investment in another monitor and a dual video card.

[Jaegen]

That's funny, because I have two monitors and now I like maximizing VI block diagrams:  I can have my LV stuff maximized on one monitor and use the other for everything else.  I think this one has to be considered personal preference.

My current pet peeve is NI example VIs with block diagram windows that aren't saved big enough to show all the code - but that's just because I've been looking at a lot of them lately.

[TCPlomp]

I stumbled upon some code which said just ' F*** you'....

The programmer was kinda annoyed by his own work that he would punish himself every time it ran....
Cursing/swearing is for me the limit. (amongst others)

Ton

[Dennis_Knutson]

7. Non-descriptive topics (i.e. I need Help)

8. Topic but nothing in the message.

9. "I get an error when running my program" and then not providing the error code.

10. Attaching only the top level VI

11...

[tbd]

... 11) sparsely populated diagrams with Loops and cases the size of Montana

12) Nailing obscure answers - and not receiving a peep of "Thanks" - or stars!

Message Edited by tbd on 03-28-2007 01:04 AM

[tst]

Opening a maximized VI may be annoying, but opening a non-maximized VI with a width of 2842 pixels on a 1024*768 can be more annoying.

---

altenbach wrote:

Block diagrams with non-white background color. (no matter what you pick, one wire type will be camouflaged ;))

---

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.

[shoneill]

Or what about front panels / diagrams appearing off-screen due to the previous user's multiple-monitor set-up.......

Shane.

Ps Tst, I agree on the "That's simply easy to forget.".  It's the only excuse I have!

Message Edited by shoneill on 03-28-2007 01:18 PM

[RayFarmer]

---

@tbob wrote:

My pet peeve is when someone posts a vi and he/she doesn't mention what version it is in.  I usually use LV 7.1.1, and when I try to open an LV 8.x vi, I get the warning message.  Then I have to close LV 7.1.1 and open LV 8.2.

---

long long long time ago, I did make a suggestion that versions were quoted as part of the message, even make the 'Post a message' mechanism ask for version(s). It would make life easier for those answering the post.

Ray.

[Ben]

I think I generally try to cut the questioner a lot of slack but my biggest peev is the reply that reads

"You can't do that in LabVIEW."

When they really should have posted

"I don't know how to do that in LabVIEW and I am not going to take the time to figure it out or ask anyone who might know."

I can't count the number of times I found myself stopping all real work to nip those falsehoods in the bud.

Ben

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