LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Linked Input Tunnel" is not accessible when trying to connect to a case selector

In the example below (all empty cases, with Case 0 connecting the Case Selector to the output tunnel), it is not possible to use the Linked Input Tunnel >> Create & Wire Unwired Cases action:

 

Screen Shot 2016-05-06 at 10.00.53.png

 

This menu is only accessible when the input is passed into the structure via a tunnel:

 

Screen Shot 2016-05-06 at 10.36.46.png

 

Now, I know that this menu is called "Linked Input Tunnel" (why not "Link Input Tunnel"?), not "Linked Input Tunnel or Case Selector", but it strikes me as a missing feature (I did not say bug).

Comments?

0 Kudos
Message 1 of 5
(4,263 Views)

What you are asking for makes sense.

 

My guess is that the selector is a different class of tunnel than a regular tunnel, and the code for linking tunnels doesn't recognize it as something that could theoretically be linked.  It is probably something that the original designers didn't think of including, and is probably a relatively rare use case.  (Many users probably don't realize that the selector behaves like a regular tunnel.)  Also, the wire branch to a regular tunnel is a relatively simple work around.

 

So what you are looking for is reasonable, unless there is some other technical reason that makes it impossible or difficult to do.  Whether it is something that is a high enough priority to make the change, that is a different question.

 

See if anyone else comments in this thread, and if it still makes sense, go ahead and add it to the idea exchange.  I'll put my Kudo to it.

 

EDIT:  While typing this message, I see Darin found it on the idea exchange.  And it looks like I thought it was worthwhile of a kudo when I saw it back then.

0 Kudos
Message 3 of 5
(4,249 Views)

Yes, for completeness, that should also be possible.

 

(We have the recently added feature that we can click any input tunnel and "replace with case selector", but if we do that using a linked tunnel, the linking is lost.)

 

I suggest to create a new idea.

0 Kudos
Message 4 of 5
(4,246 Views)

The idea linked to by Darin K. directly addresses this question. I kudo-ed it.

I must have done my search with the wrong keywords, because a search with "Linked Input Tunnel" returns this thread as one of the first hits:

Bug report: attempting to link a tunnel to the case selector, which links to a similar idea at the end.

Message 5 of 5
(4,236 Views)