BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

UWO's (Unidentified Wiring Objects)

UWO:

a mysterious object seen in LV for which it is claimed no orthodox scientific explanation can be found, often supposed to be a vehicle carrying extraterrestrials.

 

Not sure about that last part 😁.

 

I'll post mine here, please feel free to add your.

0 Kudos
Message 1 of 7
(2,817 Views)

Ran into this one. Saw it before, but never cared to look further:

wiebeCARYA_1-1676627243516.png

 

I demystified it, but see if you can.

 

Hints:

It's not the for loop's iteration or conditional terminal

It's a nested part of the VI.

 

Steps to reproduce:

Spoiler
Make 2 nested for loops
Select the top for loop's iterator terminal
Select Move To Front from the VI's menu
Move the iterator 'over' the other for loop
(Optionally) Hide the iterator.

 

Message 2 of 7
(2,813 Views)

I see stuff like this from time to time.

First reaction is to scroll the diagram down out of the visible region and back again to see if it disappears, in which case it's just a redraw glitch.

0 Kudos
Message 3 of 7
(2,741 Views)

@Intaris wrote:

I see stuff like this from time to time.

First reaction is to scroll the diagram down out of the visible region and back again to see if it disappears, in which case it's just a redraw glitch.


I also see the text "Filter.." often in my front panel.

 

It seems like a glitch from the quick drop or find dialog.

Of course, catching it in the act is hard when you actually want to.

0 Kudos
Message 4 of 7
(2,738 Views)

wiebe@CARYA wrote:

@Intaris wrote:

I see stuff like this from time to time.

First reaction is to scroll the diagram down out of the visible region and back again to see if it disappears, in which case it's just a redraw glitch.


I also see the text "Filter.." often in my front panel.


Here's how I get it:

 

Create a new VI

CTRL+F

Find anything (text or object)

wiebeCARYA_0-1676895061910.png

 

Message 5 of 7
(2,725 Views)

FYI, the 'Filter' artifact text issue has already been filed to LabVIEW R&D as Bug 2259162 and is scheduled to be fixed in a future LabVIEW release.

Message 6 of 7
(2,704 Views)