Lv2013 SP1, although it happens on LV2010 and earlier versions too. See the JING: <http://www.screencast.com/t/hRGVmHSol> The VI is broken. I renamed a USER EVENT elsewhere, and this VI that uses it, doesn't know about the new name. So, it's broken. I get that. At 0:13, I edit the events for this case and choose the new name. That should fix it. But..... it's still broken. I wonder what else is broken? How do I find out? Well, I click on the broken arrow, of course. But, then LabVIEW decides "Surprise! I was only kidding - it's not broken after all - Here, I'll RUN IT FOR YOU!" Obviously, the compiler is not being triggered at the right time. Is this related to that Environment / Compiler Optimizations setting? Maybe somehow it thinks that lying to me is a better option than taking an extra millisecond?

LabVIEW

We could testify that you find the craziest bugs! However that could lead to inferences of the "it takes one to know one" category.

Lynn

Message 11 of 11

(647 Views)