LabVIEW Idea Exchange

[#1]

LabVIEW is a “Graphical Programming Language”, it is compiled and executed according to code represented graphically; however, it is possible to have two different codes with the same visual representation but with different behavior.

Ex.    Can you tell the difference between the two sections of code below?

VI  1:                                                                                    VI  2:

                        

The “VI 2” has the second subVI over the error cluster wire without being connected to it, but you cannot notice it unless you move the subVI. Error cluster terminals are recommended; so, you will be able to run the VI with the error cluster terminals disconnected (without having the run arrow broken).

VI  1:                                                                                      VI  2:

                        

Suggested Solution:

Perform an “Auto Clean Up Wire” to the wire(s) or wire segment(s) that is under a subVI every time a subVI or function is placed over a wire(s).

“Auto Clean Up Wire” when the subVI is released over the wire.

[#2]

This way you will be able to debug your code a little bit easier.

[#3]

I was thinking that it would also be a nice option to be able to insert the function if the wires running underneath are of the same type as the overlying terminals.

[#4]

Hi dj3,  I agree about the auto-insert if the terminals are the same type as the wire underneath.

The idea is that LabVIEW should not allow having wires going into subVI’s or functions if they are not actually connected to them.

[#5]

"The idea is that LabVIEW should not allow having wires going into subVI’s or functions if they are not actually connected to them."

At the very least a wire going under an icon without connecting to it should be visibly different from a wire connected to an icon.  It's not the same logically so it shouldn't be the same graphically.  Maybe little black dots, or a grayed-out effect starting a few pixels out?  How about if the wire layed on top of the icon instead of under it?  I don't know how to do it, but there should be a visible "Hey, these aren't connected, it's just an overlap' type indicator.

[#6]

"At the very least a wire going under an icon without connecting to it should be visibly different from a wire connected to an icon."

I disagree Labview should prevent wires from being routed under another graphical element.  I do it all the time in situations where routing around the element would make the diagram more complicated.  However, I think the above suggestion is good. 

Labview already has a way of showing us crossing wires are not connected.  It inserts a 1 pixel gap between the two wires.  (See case 2.)  Why not simply extend that to vis (and case structures, loops, etc) where a wire appears to enter or leave the element but does not actually connect to it?  (In the example below I increase the gap to 2 pixels to increase visibility.)

[#7]

Hi, To avoid issues with badly wired wires, and detect them better what about showing the wires OVER the subvis ?

[#8]

VI Analyzer is a tool capable of detecting and pointing out situations like the described one.

I was not aware that Block Diagram Cleanup does not move the functions as such that overlayed wires are still "hidden". So this is either some kind of bug report or you should add VI Analyzer into your toolsuite for capturing issues like this....

Norbert 

[#9]

I don't like the idea of an auto-wire cleanup since you don't always place a VI correctly the first time. Accidentally dropping a VI on an existing mass of wires would be REALLY annoying. Especially if you spent some OCD time making them look nice.

I like the idea of having a better visual representation of no connection. Make that an idea!

[#10]

“I don't like the idea of an auto-wire cleanup since you don't always place a VI correctly the first time. Accidentally dropping a VI on an existing mass of wires would be REALLY annoying.”

I have accidents once in a while but LabVIEW gives the opportunity to “undo” many steps back.

I haven’t noticed the gap between not connected crossing wires; I’m used to pay attention to the big dot when they are actually connected. I believe that the small gap may not work to have a clear visual representation of no connection; the wire on top of the icon is better than the way it is right now. I still prefer the “Auto Clean Up Wire”.

[#11]

This is similar to the behaviour of structures when they grow. Why not extend that functionality to the whole block diagram?

Personally, I am shocked and often very frustrated that Labview even allows code to be covered (try doing that with a text-based language). However, I appreciate there are some people who may choose to do so. In this case, the underlying code could be shown as a lightened colour or grey/black silhouette.