Community Nugget: Clear up your front panel a bit

[Broken_Arrow]

---

TCPlomp wrote:

---

Broken Arrow wrote:

Speaking of labels, I have never liked the fact that Sub-VI terminals take on the Caption name and not the Label name, if a caption exists. I think it should be the label and that's that.

---

Broken Arrow could yu explain that a little bit?

Are you in favor of the caption or the label?

---

The Label.

[JÞB]

While we are at it- fix the name to

"Error In"  with leading capitalization per style guide. 

Now my take on "Variable Name (default)"  I quite agree with Ben on this one.  STOP using the (default) and automatically place this property in the tip-strip without an override- it must show if tip strips are showing!

My justification being specifically that quite often the default value changes and the lables are not updated (It would require instances in callers not in memory to need to recompile) very undesirable- oh and break any callers that use the lable property (such as every vi referance, property etc...) So we have mis-documented the code and promoted obsolete lables   This is not my idea of "Well-documented, Maintainable code."  In fact  I'd have to say that after consideration- Variable(default) is poor programming practice from a technical point of view

Thanks for getting me to think about it- Generally I don't challenge the style guide- but this point should be carefully re-evaluated!

[Darin.K]

Excellence will never be standardized, only mediocrity.  Cast off the shackles of the style guide, strive for excellent code and eventually today's excellence will be tomorrow's standard.  Where did this mythical style guide come from (I have never seen it myself)?  I'll assume it codifies what was assumed to be best practice at the time, this is subject to change but it takes someone to lead the charge.

[smercurio_fc]

---

Darin.K wrote:

Where did this mythical style guide come from (I have never seen it myself)? 

---

It was originally a separate document, but has since been incorporated into the LabVIEW Help.

[Ben]

---

Darin.K wrote:

Excellence will never be standardized, only mediocrity.  Cast off the shackles of the style guide, strive for excellent code and eventually today's excellence will be tomorrow's standard.  ...

---

Darin,

You just made teh LV Proverbs list (again). That would make a very nice signature (nudge nudge, wink, wink, say no more, say no more).

I'll see what I can do about leading from the back seat.

Ben

[Darin.K]

---

smercurio_fc wrote:

---

Darin.K wrote:

Where did this mythical style guide come from (I have never seen it myself)? 

---

It was originally a separate document, but has since been incorporated into the LabVIEW Help.

---

What is this mythical LabVIEW help?

[Andrey_Dmitriev]

---

 I know the default value is no error. It's obvious. I don't need it in my face with every single error cluster.

---

Hmmm.... I think, it also well known that this cluster is error cluster, boolean is status, numeric is code and string is source, so you can simply remove all texts from this cluster without lost any functionality, isn't? 🙂 

Andrey.

[JÞB]

Style Guide

Not a myth- check pg 6-20 

[Ben]

Still no reasons why to keep that rule?

Ben

[GregFreeman]

---

What is this mythical LabVIEW help?

---

It's the place you go AFTER you ask your question on the forums, only to realize, your answer was there already! 🙂