03-31-2006 11:39 AM - edited 03-31-2006 11:39 AM
Message Edited by Ben on 03-31-200611:40 AM
03-31-2006 11:53 AM
If you force a re-compile of the VI (ctrl-shift-click Run arrow), the problem goes away. Also, it appears to be fixed in the next version of LabVIEW as well (i.e., the VI does not open broken).
-D
03-31-2006 12:13 PM
Hi Darren,
That worked at this end but...
When you say "next version" is that 8.0.1 or are you talking about the un-released LV 8.1?
If you are talking about LV 8.1 then is there a CAR for this issue?
I ask becuase I have heard of bugs being fixed in the "next version" before the release, only to find out it was later "un-fixed".
Ben
03-31-2006 12:14 PM
03-31-2006 12:21 PM
Now I am really confused.
Well at least you have been warned.
Ben
03-31-2006 12:47 PM
I didn't try it in 8.0.1, so that's good news that it appears to be fixed there.
Jeff: When you force re-compiled, did you do Ctrl-Shift-click to force recompile all? That's what I had to do to get it to work...just a force recompile of the VI (Ctrl-click) did not work.
-D
03-31-2006 02:07 PM - edited 03-31-2006 02:07 PM
Hey Ben,
Sorry for the confusion, I may have been running in a debug version of LabVIEW 8.0 that shows warnings at a higher granularity than the release build. These are things that allow us to catch unexpected scenarios during development, but are situations that aren't catastrophic to LabVIEW's execution such that a crash would occur. I'd guess that's why you didn't see the warning.
And Darren - good point, I'd read your first message too quickly - I didn't include SHIFT on my recompile, so the CTL file probably wasn't getting re-compiled and therefore the problem wasn't going away.
Take care,
Jeff
Message Edited by Jeff B on 03-31-2006 02:08 PM