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
When a wire enters and leaves at different heights, it's a visual cue that the VI is wired correctly.
When a wire enters and leaves at the _same_ height, perhaps only the input is wired - you can't tell.
(There are two kinds of LabVIEW programmer: those who have been "bitten" by this bug, and those who will be.)
I'd argue these problems can happen anywhere, even when the inputs and output aren't aligned. And VI Analyzer is the tool to look for wires hiding behind objects. Wire cleanup and BD cleanup would also fix it if you don't mind that it may also change other parts of the wire or diagram.
When a wire enters and leaves at different heights, it's a visual cue that the VI is wired correctly.
When a wire enters and leaves at the _same_ height, perhaps only the input is wired - you can't tell.
(There are two kinds of LabVIEW programmer: those who have been "bitten" by this bug, and those who will be.)
I'd argue these problems can happen anywhere, even when the inputs and output aren't aligned. And VI Analyzer is the tool to look for wires hiding behind objects. Wire cleanup and BD cleanup would also fix it if you don't mind that it may also change other parts of the wire or diagram.
I'd argue that an uwired-connector bug is not likely to be accompanied by a bend that's behind VI and also happens to exit from correct terminal.
So,a masked-bug problem is extremely unlikely to happen - unless connectors are aligned.
I'd prefer not to complicate my job by adopting habits that increase the likelyhood of bugs and require extra work/tools to validate.
It's easier to avoid bugs by using inherently-safe(er) coding practice.
Re-opening because LabVIEW NXG has been discontinued.