LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
joerg.hampel

Structure labels visible by default

Status: New

I'd love to see an option for the label of structures to be visible by default, similar to the already existing "Subdiagram labels visible by default" option.

 

structure labels visible by default.png




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


15 Comments
AristosQueue (NI)
NI Employee (retired)

Restricted to some case structures, the value of those comments makes sense, but since even you do not use them on all case structures, and since there are times when other ways of supplying comments would (in my opinion) be more valuable, I'd still not turn on the option if it became available.

joerg.hampel
Active Participant

Well, if nothing else, this discussion has helped me sharpen the definition of what I want our style guide to cover (and what not), and reinforce my feeling that it’s of importance to our own use case. 

Thanks to everybody. And if this idea does make it into LV, I‘ll still be first to turn it on 🙂




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


bhpowell
Member

Interesting thread.

I, for one, would probably never turn on this option.

For context, I turned on the option to show constant labels by default, but turned it off after one day because it was too much. Do I really need a comment to tell me that my format string is a format string, or that my URL is a URL?

As AristosQueue knows, I come from a background where one assumes the code needs no comments, and then one adds a few where it helps with readability.  It’s not a philosophy of “no comments”, by any means.  It’s more of an attitude that the comments are there only when they’re needed, not just to satisfy a style guideline.

(But I have nothing against style guidelines and their authors who believe otherwise. 🙂 )

I guess stated another way, my philosophy is that I add comments until the code feels right, and I like that better than removing comments until the code feels right.

 

Brian

 

Brian Powell
Stravaro, LLC


Learn more about the DSH Pragmatic Software Development Workshops.
AristosQueue (NI)
NI Employee (retired)

> Do I really need a comment to tell me that my format string is a

> format string, or that my URL is a URL?

 

In my case, yes, because we use that label to tag whether or not a string constant should be localized. Not something most teams have to worry about.

benjamin-hinrichs
Member

I support this feature request for case structures. I use this style and find it helps readability in many cases. Knowing the question being asked helps to understand the code within. 

 

Slightly off-topic: I use the constant with labels option and found it helps me when I'm developing because it reduces some dumb mistakes like wiring row/column in Array Index function wrong.

----------
Although I've been 10+ years long fan of LabVIEW, I started to discourage engineers to start new projects in a SaaS language. NI must first regain trust within its community.