Nasty Tunnel behavior

[JÞB]

Warning, The following actions were performed on a closed course by a professional LabVIEW Developer.  Do not try this at home.

Not exactly the behavior I would have chosen I had hoped it was merely cosmetic.  So I tried this:

And Error did not propagate A ctrl+u showed why

another obscured SR Unitiallized!   That little cosmetic flub could really cause a largeish headache for a developer that does not show warnings by default in the error list.... Of course I do

[crossrulz]

I remember complaining about that stuff (or similar) during the 2012 beta.  I thought they had it fixed, but I guess there were some cases they missed.

[Mark_Yedinak]

If you run the VI analyzer on it does it report it as a hidden object? While not a true fix it would provide a way to find them.

[JÞB]

---

@Mark_Yedinak wrote:

If you run the VI analyzer on it does it report it as a hidden object? While not a true fix it would provide a way to find them.

---

I would assume so... its in the error list as a hidden object warning.  I'm fairly sure the VI Analizer test keys off the compiler warning. 

[johnsold]

This looks like it could be linked to the wiring through the label bug found by X. last month.

Lynn

[JÞB]

---

@johnsold wrote:

This looks like it could be linked to the wiring through the label bug found by X. last month.

Lynn

---

Probably closely related by feature introduction.  You got to love new features! NI comes up with all these cool new toys and we promptly abuse them and break things. 

I imagine Yair might stop by and tell me the compiler really should break the code with that warning.  I'm beginning to make his point for him and none of those Kudos is mine (For now at least)