LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
tst

Get rid of the "(no error)" part of the error cluster

Status: Completed

Available in LabVIEW NXG 1.0. The error terminal names for nodes are now 'error in' and 'error out'.

There's a common convention in LabVIEW where if a control is not a required input, you place the default value in parentheses:

 

WhatToDoTonight.png

 

 For the most part this make sense and is useful when calling VIs, but there is one place where it's really annoying:

 

 

No_Error.png

 

 

We know there's no error by default. I suggest that NI simply remove this. This can be done today by going to <vi.lib>\errclust.llb and modifying the control, but that's annoying to do with every installation.

 

I would even go so far as to say that NI should write a VI which will go through vi.lib and remove the text from all the existing VIs. I doubt this would have any backward compatibility issues, because I think the only place where those would be relevant is if someone is calling a VI in vi.lib dynamically AND setting the error in value, and frankly, those people deserve to be punished.

 

 


___________________
Try to take over the world!
26 Comments
tst
Knight of NI Knight of NI
Knight of NI

Ignore the performance thing I was talking about. It's completely irrelevant.

 

The annoyance argument is far from weak. I spend a lot of time moving into and out of VIs. In each VI, the "(no error)" part of the label appears in the diagram. That's where it takes up room which annoys me, especially if there's a case structure there.

 

 

 


I would argue against any time being saved by developers leaving out this text. If this text is left out, you'll want to open the VI and verify that some non-default value has not been set, as you can't determine whether the developer was using a default value, or forgot to program in good style.

 


 

 

Maybe you would, but to me that would just indicate you didn't understand the other idea - the point of that idea was that LV would add the default value automatically, so you would see the actual default value. The current convention, at best, tells you that the developer intended to provide a default value behavior, not that they actually did it correctly.

 

In any case, since that talks about the other idea, it's not relevant here. If you have comments on it, you should post them there.

 

 


___________________
Try to take over the world!
Darren
Proven Zealot
Status changed to: In Development
 
Lars-Goran
Member

Very late comment to this idea already in development, but here goes:
Define the error in control without "(no error)" in its name, and whenever it is assigned to a lower left

connector pane terminal it should automatically become a required input. As a consequence it then becomes necessary to connect a "no error" constant in the few cases where no error wire is supposed to be used for the input. Preferrably Smiley Wink like this, with a home made, space saving, no error constant:

No error constant

See also this related idea: Right-click option on error in terminal

 

In the few cases where the input by purpose is selected to be optional, the programmer will have to change the name to include the "(no error)” part and set the terminal to ”optional”. As we are all lazy, this bad (in my view) behaviour will be minimized Smiley LOL

Darren
Proven Zealot
Status changed to: Completed

Available in LabVIEW NXG 1.0. The error terminal names for nodes are now 'error in' and 'error out'.

Darren
Proven Zealot

Related to this idea, I have posted a right-click plugin for LabVIEW 2015 and later that will remove the "(no error)" text from the label of any error control you create when right-clicking a terminal and selecting 'Create > Control'. You can download the plugin here.

CuriousSwede
Member

Yes, and the format "error in (no error)" is simply wrong. The default value of a cluster should be (if at all) stated for each component, i.e. in this case error in (False,0,"").