LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Antonio_lara

"Teleport wires"

Status: Duplicate

Many of my VI's have lots of long wires that go from one end of the block diagram to the opposite end. It would be nice to create some kind of block, to which you can connect as many wires as you want, and a twin block that you can place where somewhere else, and get the wires out of it, this way, all the wires across the vi won't be seen, and everything will be more tidy.To distinguish different wire blocks, a solution could be to change the block color, or edit the icon as you can do with sub VI's 

8 Comments
elset191
Active Participant

Duplicate.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-breaking-up-long-wires-with-labels-in-each-end/i...

also this one kind of. http://forums.ni.com/t5/LabVIEW-Idea-Exchange/wire-jumping-across-case-structure/idc-p/965347

 

I think there's another one out there but I can't find it now

--
Tim Elsey
Certified LabVIEW Architect
tomlawton
Member

Bundle to a (hidden) cluster control at one side... Unbundle from local variable of said cluster at other side...? That even names the terminals for you... 😉

Antonio_lara
Member

ok, thank you!!  I hadn't thought of that 🙂

X.
Trusted Enthusiast
Trusted Enthusiast

@elset191: maybe this one

elset191
Active Participant

@X wrote:

@elset191: maybe this one?  


Yup.  I was picturing the images in my head.  Searched for something along the lines of "buried wire" but it didn't turn up (when I search that now I see it, though.  Curious)

--
Tim Elsey
Certified LabVIEW Architect
AristosQueue (NI)
NI Employee (retired)

tomlawton wrote:

> Bundle to a (hidden) cluster control at one side... Unbundle

> from local variable of said cluster at other side...? That even

> names the terminals for you... 😉

 

NO. tomlawton, you are cruel to suggest this to Antonio_lara. This is not a workaround. This is a serious programming error that has severe ramifications for the actual runtime correctness of your program. For one thing, you just introduced a quadruple data copy (once into the cluster, then the cluster into the control, then the cluster out of the control, then the bundled value out of the cluster). Then there's the race condition bug if you don't have an ordering between your write and your read guaranteed, which is easy to screw up.

 

Wire the wire. If your diagram is too large, create subVIs as needed. SubVIs pay lots of benefits for code readability, testability and reusability. Going beyond the size of a single screen is strongly discouraged by every LV style guide (with a couple exceptions for long scripting-like operations), and it is because of issues like this one.

MaryH
Member
Status changed to: Duplicate
 
X.
Trusted Enthusiast
Trusted Enthusiast

You do not want to create subVIs when your wires carry loads of data, as it will generate copies. And you know how LV handles out of memory errors: RECKLESSLY.

I think you guys need to do some real life heavy calculations with LV to start feeling our pain.