LabVIEW 2022 Public Beta
Broken Wire Usability Issues
It looks like this wiring behavior is the same as 2020 but I found it when messing around with the Search 1D Array VIM. Attached is a video demonstrating it. It looks like what happens is a segment of a wire is intentionally broken, and then if the rest of the wire becomes broken, and then an Undo is performed. Then the wire appears broken when it really isn't. The Undo should return the VI back to the way it was. At the end of the video you can see a broken wire, but the run arrow is seen.
Hi Christina,
I really don't agree with the outcome here.
Wiring in LabVIEW is so fundamental, you cannot gloss over this kind of thing.
This behaviour shown above is clearly a bug that I would find extremely annoying. Hopefully this issue reported is just a weird corner case with VIMs and undo... otherwise this version is definitely a skip for me.
@Neil.Pate wrote:
otherwise this version is definitely a skip for me.
I tested it back in to version 2020 and the issue was there then too. It likely exists since VIMs were added.
@Hooovahh wrote:
@Neil.Pate wrote:
otherwise this version is definitely a skip for me.
I tested it back in to version 2020 and the issue was there then too. It likely exists since VIMs were added.
I do seem to wire them in a way that I get this all the time, right from the beginning.
The only way out seems to be to delete the vim and put a fresh one on the BD.
Probably hash and compile cache related?
Search LabVIEW like a graph! 
Since the introduction of the search 1D array.vim, I am typically getting annoyed by unnecessary broken wires.
In 80% of the cases, I am searching boolean arrays for TRUE and this temporarily breaks the code (unlike the classic search 1D array).
For example, Wiring a boolean array to the top will break the wire for no obvious reason until we wire a boolean scalar to the element input. Beginners might stop after the first step and conclude that the function does not work for booleans at all! 😞
