06-07-2006 03:40 AM
06-07-2006 03:53 PM
Hello Clemens,
I have also seen this in LabVIEW for Windows (7.0 and 7.1) with VIs that got some improvements in 7.1 and were saved for previous to have that functionality in 7.0, too. Then the 7.0 VIs got some enhancements and then got used in 7.1. Later on (again after having made further enhancements in 7.1) the VIs ware again saved for previous ...
This scenario took place on several PCs, some of them having LabVIEW in German, others the English version installed. Regrettably I could never reproduce a broken run arrow. So there is no way to predict when it happens to you.
But in LabVIEW for Windows you can easily circumvent to close all windows and get rid of a "wrong" broken run button by holding down the "Control" button and left-mouse-button-clicking the broken run button.
This makes LabVIEW recompile this VI and update the appearance of the run button. (I hope this also applies to LabVIEW for Linux?)
This is useful to circumvent to close LabVIEW and allows you to continue working with your VI and window arrangement.
By the way: Holding down "Control" and "Shift" and left-mouse-button-clicking the run button will compile all VIs in memory. This is a good idea for a tree of VIs that strange-behave like yours. I have come to the impression that a compile of the entire VI hierarchy is a good idea when observing unexpected behaviour with quite old code.
Be aware that all VIs in memory needs to be saved after the recompile. If you quit LabVIEW without saving the hierarchy, you had better saved the time of the recompile.
Hope this helps, Guenter
06-08-2006 06:00 AM