LV 2010 Strange Broken Run-Arrow

[Jordan Kuehn]

The referenced front panel item is not hidden and is just fine. However, when I resize the Merge Errors vi it fixes everything. This is repeatable. Why would a missing input on the Merge Errors vi throw the other two errors?

[asbo]

Tough to diagnose without a block diagram. Can you post it?

[Cat]

I get something like this on occassion, too (LV2010). Sometimes there's some broken wire somewhere that has nothing to do with the "hidden control". Fix it, and the error goes away. Don't have a clue what's causing it, but once I figured out it would go away if I fixed everything else, I started ignoring it.

[Jordan Kuehn]

Tough to diagnose without a block diagram. Can you post it?

[SuperS_5]

Hi,

The message is related to the fact that your references are not defined types, just generic controls. On my system they are just warnings not errors. Maybe the error window gets a little confused sometimes.

[Jordan Kuehn]

Hi,

The message is related to the fact that your references are not defined types, just generic controls. On my system they are just warnings not errors. Maybe the error window gets a little confused sometimes.

I can buy that; however, they are not listed under warnings once I fix the extra input terminals on the merge errors.

[Djed]

Can you file a bug report on this or post some (preferably simple) VIs that reproduce this issue and I'll file a report. I have an idea of one thing might be going wrong internally.