LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
X.

Conditional indexing should accept Error Cluster

Status: New

The For/While Loop conditional indexing feature (new in LV 2012) is neat but so far only accepts a Boolean. That's departing with the behavior of the Case Structure selector terminal, which accepts error clusters:

 

ScreenHunter_007.jpg<----------- I'd like to connect the error cluster wire in the For Loop directly to the indexing condition terminal

(the case structure outside is just here to show what I mean by connecting an error cluster to the condition terminal of the Case Structure).

Of course the workaround is simple (as shown), but why introduce an even simpler approach for the Case Structure and not offer it here?

 

Edit: The obvious objection is that some will want to index when there is an error, other when there is none, which in fact might be best handled by the approach shown above. An error cluster connection would need a different contextual menu as well (index on error or index on no error).

 

16 Comments
fabric
Active Participant

[Off topic: Do you REALLY colour all your diagrams "buttered popcorn"? Smiley Tongue ...or is it an artefact of the screen capture tool you use??]

X.
Trusted Enthusiast
Trusted Enthusiast

It's actually "cat pee". It soothes me.

AristosQueue (NI)
NI Employee (retired)

We discussed this when implementing the feature. When error cluster is converted to Boolean in all other cases, it is "error" that equates to True (i.e, when you connect to an Or or an And primitive). It was weird to invert the meaning for the filter.

X.
Trusted Enthusiast
Trusted Enthusiast

You have found a solution for Loops:

 

ScreenHunter_001.jpg

crossrulz
Knight of NI

X, look at the logic involved between the two.  The loop termination will stop when there is an error (T status = T stop).  For the conditional index, you are asking for the opposite (T status = F index).  It does seem counter intuitive once the details are looked at.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
X.
Trusted Enthusiast
Trusted Enthusiast

I am just saying, the question mark icon could be replaced by a variation on the loop condition icon so that the user can choose whether to index on error or not.

X.
Trusted Enthusiast
Trusted Enthusiast

The more I use the conditional indexing feature, the more I wished it would be capable of autoindexing on False rather than True.

Thus, Suggestion extension: allow autoindexing on False (or equivalently, allow inverting the conditional terminal).

AristosQueue (NI)
NI Employee (retired)

X: Yeah, the "invert logic" option was discussed... put a little circle in front of the terminal, like we do on Compound Arithmetic node for inverted terminals. Got cut to keep the scope of the feature down to make the release. Might add it in the future, but it now goes back in the pool of features we might someday do. Still wouldn't help the error cluster problem -- there's just not that much visual space to put alterate icons on the terminal, and without a clear indicator of which way the issue is being decided, it's just unintuitive.

jacemdom
Active Participant

Maybe coloring the question mark red when indexing on error and leaves as is for indexing on no error.

AristosQueue (NI)
NI Employee (retired)

jacemdom: That option was rejected by color-blind team members. For them, it's already enough of a problem on loop conditional terminals that there isn't also a glyph change, we shouldn't compound it on newer features.