LabVIEW
bug! duplicating conditional tunnels in loops
Solved!
I wonder if this one has been reported already. It is serious enough, leads to immediate crashes, and I now found it in all versions from 2012 to 2017, under linux and windows.
It goes like this: start from a loop (while or for) with a conditional tunnel like this one, whatever data:
Now select the tunnel and all what is connected to it:
Drag it downwards, holding Ctrl, to duplicate it. This is the result:
Notice that the new tunnel is looong. Removing the selection you realize that this tunnel cannot be grabbed, and that there are wires going nowhere.
At this point the VI is well screwed up. You can try to save it, you can try create a snippet of this result, you can press on the run arrow - they all cause an immediate SiGSEGV.
Can some PTB check if there is already a CAR for this, or escalate?
@Enrico_Segre wrote:
I wonder if this one has been reported already. It is serious enough, leads to immediate crashes, and I now found it in all versions from 2012 to 2017, under linux and windows.
It goes like this: start from a loop (while or for) with a conditional tunnel like this one, whatever data:
Now select the tunnel and all what is connected to it:
Drag it downwards, holding Ctrl, to duplicate it. This is the result:
Notice that the new tunnel is looong. Removing the selection you realize that this tunnel cannot be grabbed, and that there are wires going nowhere.
At this point the VI is well screwed up. You can try to save it, you can try create a snippet of this result, you can press on the run arrow - they all cause an immediate SiGSEGV.
Can some PTB check if there is already a CAR for this, or escalate?
Fortunately you can ctrl+Z out of it. BUT if you think you got rid of the issue by deleting the offending code - it seems that the elongated tunnel is a redraw artifact and will go away if you resize the FOR loop structure - you're in for a rude surprise when next you try to run or save it. Like maybe after you've done some significant coding.
