Pass-through Register

[Minions]

I was thinking that it would be nice if there was a default connection of a pass-through register.  Similar to the shift register only here it would pass the input to the output by default rather than having to wire each case.  If there is a wire into the output, the default connection is NOT selected.  In the snippet, both the top and the bottom outputs are the same for this case.  It would make for cleaner looking block diagrams if the only thing happening in a particular case is the wiring of an input to an output.

[Mythilt]

How would you know which output was attached to which input if you had multiple inputs and outputs?  A simple arrow like you have would not suffice when you have two pass-through inputs and outputs, and you can't just say look at a case where the two are wired, since those cases might not be a simple straight wire out.

I'm not against some way of simplifying the wiring when all the data is doing for that case is entering and exiting, but I think your example would end up making the situation more complex and prone to error.

[Minions]

I made reference to the SHIFT REGISTER.  A shift register passes the output back to the input.  Here it would pass the input to the output.  As such, the signals would remain in-line.  This would allow for numerous inputs to use the pass-through as they would be 'default wired' directly across.

[crossrulz]

Similar: A better way to define the output of unwired output tunnels

[AristosQueue (NI)]

Feature already exists (I think LV 2013 but possibly earlier).

Right-click on the right-side tunnel and choose "Linked Input Tunnel >> Create". The other items under the "Linked Input Tunnel" menu are also useful. See LV online help: http://zone.ni.com/reference/en-XX/help/371361K-01/lvhowto/wiring_tunnels_auto/

[Darren]

Right-click on the right-side tunnel and choose "Linked Input Tunnel >> Create". The other items under the "Linked Input Tunnel" menu are also useful. See LV online help: http://zone.ni.com/reference/en-XX/help/371361K-01/lvhowto/wiring_tunnels_auto/

[crossrulz]

Linked Tunnels were from LabVIEW 8.6.  I abused that feature when it came out.

[Mythilt]

@AristosQueue (NI) wrote:

Feature already exists (I think LV 2013 but possibly earlier).
 
Right-click on the right-side tunnel and choose "Linked Input Tunnel >> Create". The other items under the "Linked Input Tunnel" menu are also useful. See LV online help: http://zone.ni.com/reference/en-XX/help/371361K-01/lvhowto/wiring_tunnels_auto/

---

From how I read the OPs suggestion and the picture, I'm pretty sure they want it so that the 'Linked Input Tunnel -> Create' action creates a connection that behaves like a wired connection, but doesn't actually draw the wire.  The action you indicate creates a link, but does not automatically take the value from the input tunnel and put it at the output tunnel without a wire connection. I know you can select Create and Wire Unwired Cases, the OP wants something where you get the same behavior as if it was wired, but without the actual wires, is how I read the suggestion.

[AristosQueue (NI)]

Jon:

If that's the correct interpretation then the idea should be Declined as "already investigated and rejected." We implemented that as one of the variations while working on linked tunnels. Indeed, that was the original suggestion that lead us to work on linked tunnels. It had a number of usability problems and ultimately we decided to not do it.

[Minions]

Jon's last assessment of my request is correct.  I determined that a majority of case statements generally only have a single case where the output is being changed and the rest are simply passing the other data points onto the next loop.  I did not show the loop with shift registers to avoid any added confusion with the case registers. 

Along the same lines here, we now have the ability to add a label to each case.  Maybe instead, have a cluster formed around the bottom of the case in the shape of a 'U' to pass events around inside of the case to the outputs without adding more spaghetti?  This way you could add an input/output pair to the case cluster or remove it based on the case.

[Intaris]

There is a precedent for exactly this feature since many years in LabVIEW.

The "Dynamic Events" terminal of the Event Structure does exactly what the OP is asking for.  It's -like- linked tunnels but does NOT require to be wired at the output.  The output terminal is quite happy to be left unwired whereupon it simply retains the value of the previous iteration.

I wish linked tunnels could work like that to be honest......