LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
patibandla

For, While loops the Loop Iteration, Loop Condition Label property Grayed

Status: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined. 

In the For Loop,While Loop  we can see the Loop Iteration and Loop Condition properties.

but  right click and open object properties. in this Label Visible Check box Grayed condition (not able to enable)

 

NI need to Enable this to write some Lable or commect for the Loop Condition.

same like Addition and Subtraction Functions.

Loop condiation properties.png

 

11 Comments
RavensFan
Knight of NI

It is just fine on my installation of LabVIEW.

 

I don't think you have a new idea for LabVIEW, but a problem with y our installation of LabVIEW.

jcarmody
Trusted Enthusiast

That was my first thought, too, but he's trying to make the lables visible on the "I" and the stop.

Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

RavensFan
Knight of NI

Okay.  I understand now.  I thought he was talking about the loops themselves.  I've never had any reason to ever think I would need to show labels on those specific parts of a loop.    And I still don't have any reason to ever need to show a label for an i terminal or stop terminal.

patibandla
Member

 

RavensFan: Thanks for your comments. I am thinking the i terminal and stop terminal are the part of While and For loop.

already For and While loop having the Object properties. if these terminal LabVIEW treates as a objects why can't they enable the Lable for these terminals.

AristosQueue (NI)
NI Employee (retired)

We could enable labels for those. We do not.

 

My personal opinion? I would say it just adds noise to the diagram. We don't show labels on tunnels or case selectors or many other parts of a node's specific syntax.

Manzolli
Active Participant

It's not there by default. If the programmer thinks it would help document his code, it is his choice. Why keep it greyed?

André Manzolli

Mechanical Engineer
Certified LabVIEW Developer - CLD
LabVIEW Champion
Curitiba - PR - Brazil
AristosQueue (NI)
NI Employee (retired)

Because the underlying code doesn't even store a field for such things, and we'd have to add code to support displaying it, moving it, saving it, loading it, etc. Thus it stays greyed.

Manzolli
Active Participant

@ AristosQueue: I was thinlking about that when I was writting. I never had the need for this feature, but why not? Now I know.

 

I guess this is a kind o idea with low priority and low impact. Let's see what other people think about it.

André Manzolli

Mechanical Engineer
Certified LabVIEW Developer - CLD
LabVIEW Champion
Curitiba - PR - Brazil
patibandla
Member

Manzolli: Thanks for comments. I think i terminal and conditional terminals no need to treat as a object . then if NI removes this Object properties window, it is good.

Intaris
Proven Zealot

I also think it's unneccessary for Loop terminaly to have labels.  Their context is already clear and their scope also.

 

But if we decide to give everything labels, where do we stop? Should labels have labels? Smiley Very Happy Smiley Tongue