04-07-2023 12:25 PM
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
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
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
04-07-2023 01:33 PM
I believe it changed in 2021, and it's not a bug.
Your viewpoint is one consideration, but consider this as well:
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.
04-07-2023 03:30 PM
04-10-2023 09:42 AM
@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.
04-10-2023 10:50 AM
To my knowledge, this fix was first mentioned in 2021 by flarn2006 here:
04-10-2023 01:19 PM
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.
04-11-2023 10:55 AM
@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.)
04-11-2023 05:52 PM
@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.
04-11-2023 10:53 PM
@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.
04-12-2023 04:53 AM
@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?