LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Did the wiring algorithm change?

I just upgraded to LabVIEW 2023 (was using 2020) and I don't know if this is a bug or intentional, but it seems the wiring algorithm changed. I notice this the most when I have error wires coming up from below a subVI or a bundle by name node. In the past, the wire used to stay fixed until the bundle by name moved over it, but now it seems to move with the bundle by name until it hits another node, then it remains fixed and allows the bundle by name to move without moving the wire. It's even worse when you have error wires coming up from under a subVI like the screenshot because when I move the subVI the wires move along with it, leaving a bend in the wire.

 

I know I missed a couple LabVIEW versions so sorry if this has been discussed, but I find it to be quite annoying.

Moving the bundle here just moves the right-vertical wire with it

bundle wire bend.png

it used to keep the wire fixed and do this, then it would latch to the wire and move the bundle and the wire together

f29a2ba5-6fdb-4b47-b48a-a149b02e5720.png

Ew, moving this subVI keeps the left vertical error wire like this rather then moving the subVI over it, latching, and then moving them together

 

subVI wire bend.png

Message 1 of 12
(2,188 Views)

I believe it changed in 2021, and it's not a bug.

 

Your viewpoint is one consideration, but consider this as well:

Kyle97330_0-1680891974725.png

I hope that you can at least agree that the middle option from before is not a good thing (crossed wires under an object, unclear which one has the corner connection).

 

The style guideline for LabVIEW has always been "Dataflow should be from left to right".  It seems that in order to support that, they made a change that makes wires that exit left or right and then move up or down now preserve that when moving left or right.

 

I have seen many people who prefer to code as you do for either space savings or to have less visible bends, but I personally am a fan of this change and I believe that the "Left to right" rule is more important than saving 5-10 vertical pixels or having one less bend.

Message 2 of 12
(2,157 Views)

This feature can be disabled by adding this key to your LabVIEW.ini:
DragAdjustWires=False
Then just restart LabVIEW to take it into account.

Message 3 of 12
(2,126 Views)

@raphschru wrote:

This feature can be disabled by adding this key to your LabVIEW.ini:
DragAdjustWires=False
Then just restart LabVIEW to take it into account.


My savior.

0 Kudos
Message 4 of 12
(2,030 Views)
0 Kudos
Message 5 of 12
(2,012 Views)

Annoying beyond belief.

 

I genuinely think the fact that not everyone is moaning about this is because they have not tried to do any real wiring work in newer versions.

 

I have made so many posts about crap like this and the general feedback is silence from NI (expected), but almost pure apathy from the community, so I have essentially given up getting annoyed.

 

LabVIEW 2023 is unusable for me because of the latest wiring changes, I have uninstalled it and will never use it.

0 Kudos
Message 6 of 12
(1,987 Views)

@Neil.Pate wrote:

Annoying beyond belief.

 

I genuinely think the fact that not everyone is moaning about this is because they have not tried to do any real wiring work in newer versions.

 

I have made so many posts about crap like this and the general feedback is silence from NI (expected), but almost pure apathy from the community, so I have essentially given up getting annoyed.

 

LabVIEW 2023 is unusable for me because of the latest wiring changes, I have uninstalled it and will never use it.


Because of the wiring issue?  I would expect not using it, say, for the licensing change, but because of a wiring algorithm issue that can be reverted?  (And is NI being apathetic in this case?  They did provide a config entry to revert the behavior.)

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 7 of 12
(1,889 Views)

@billko wrote:

@Neil.Pate wrote:

Annoying beyond belief.

 

I genuinely think the fact that not everyone is moaning about this is because they have not tried to do any real wiring work in newer versions.

 

I have made so many posts about crap like this and the general feedback is silence from NI (expected), but almost pure apathy from the community, so I have essentially given up getting annoyed.

 

LabVIEW 2023 is unusable for me because of the latest wiring changes, I have uninstalled it and will never use it.


Because of the wiring issue?  I would expect not using it, say, for the licensing change, but because of a wiring algorithm issue that can be reverted?  (And is NI being apathetic in this case?  They did provide a config entry to revert the behavior.)


The issue specifically Neil is talking about is the forced font size for property nodes, Bundle and Unbundle By Name, etc.  The size NI fixed to did not match was Neil (and his team) were using, causing lots of new wire bends.  For those of us using the default fonts since Windows 7 came into being have seen no changes.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 8 of 12
(1,849 Views)

@crossrulz wrote:

@billko wrote:

@Neil.Pate wrote:

Annoying beyond belief.

 

I genuinely think the fact that not everyone is moaning about this is because they have not tried to do any real wiring work in newer versions.

 

I have made so many posts about crap like this and the general feedback is silence from NI (expected), but almost pure apathy from the community, so I have essentially given up getting annoyed.

 

LabVIEW 2023 is unusable for me because of the latest wiring changes, I have uninstalled it and will never use it.


Because of the wiring issue?  I would expect not using it, say, for the licensing change, but because of a wiring algorithm issue that can be reverted?  (And is NI being apathetic in this case?  They did provide a config entry to revert the behavior.)


The issue specifically Neil is talking about is the forced font size for property nodes, Bundle and Unbundle By Name, etc.  The size NI fixed to did not match was Neil (and his team) were using, causing lots of new wire bends.  For those of us using the default fonts since Windows 7 came into being have seen no changes.


That makes more sense.  Now I see why he wouldn't want to upgrade and destroy all his block diagrams.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 9 of 12
(1,813 Views)

@billko wrote:


  (And is NI being apathetic in this case?  They did provide a config entry to revert the behavior.)


They did? To adjust the new behaviour in 2023? Can you share this?

 

0 Kudos
Message 10 of 12
(1,783 Views)