input of conditional terminal should be "pass through."

[ouadji]

the input value of the conditional terminal should  " pass through "

                  (like the "case selector" of the "Case Structure")

                   

                                                         like this,

                   

[AristosQueue (NI)]

GregS: I don't know about you, but the optical illusion there makes it look to me like that is still a full-width box. You need to lose two more pixels of width to really make it look like "this is only a left-side terminal".

[JÞB]

Thinking a bit outside the box.  I do that now and then

The key points being contended are:

• What is a loop output tunnel?
• What is a tunnel modifier?

The RCM clearly delineates between changing tunnel mode and adding a modifier terminal with a horizontal seperator.  Well, thats clear for advanced users- the sublty might easilly be lost for 90+% of users.

So how can we get information to users in a easy to find and understand manner? Help is not usually avalable in a RCM contex.  That could be fixed!

Two other things would need to happen:

• Clicking Help for Tunnel Mode would open "Conditionally Writing Values to Loop Output tunnels"
• That "How To" section of the help should be renamed dropping the word "conditional" and haveing explaination sections for "Mode" and "Modifier" 

Or better yet. a nice clear section on loop outputs that makes sence linked to some great example code, hopefully with a working "Open Example" link.  Not all the help to example code links work

[X.]

This conditional connector is some kind of mutant with special power.

Witness this:

The conditional indexing menu is perfectly functional and you can do this:

or that:

and creating an indicator works fine:

But wait! Is it actually capable of concatenating strings?

Let's try to create a control:

False alarm...

[wiebe@CARYA]

Another discussion about the same topic:

Tunnel Mode Conditional ... output condition - NI Community