hfettig Posted February 9, 2009 Report Share Posted February 9, 2009 Hi folks, This was fixed by uninstalling and re-installing VI Tester but you might still want to know. Could be a palette refresh problem. After I installed VI Tester for the first time I did get the palettes for VI Tester but the only things populated were the sub palettes. I un-installed and re-installed and now it works fine. Maybe the palette refresh was called too early? Cheers, Heiko Link to comment Share on other sites More sharing options...
Omar Mussa Posted February 9, 2009 Report Share Posted February 9, 2009 After I installed VI Tester for the first time I did get the palettes for VI Tester but the only things populated were the sub palettes. This is strange, we'll look into this but so far haven't seen this happen internally. Was this the same (8.6) installation that had the mass compile issue you reported? I un-installed and re-installed and now it works fine. Maybe the palette refresh was called too early? I'm glad you were able to get up and running! Let us know if you find any other issues! Thanks, Omar Link to comment Share on other sites More sharing options...
Omar Mussa Posted February 10, 2009 Report Share Posted February 10, 2009 Could be a palette refresh problem. Update: We were able to reproduce this problem, but we're still looking into what happened. We still haven't reproduced the mass compile dialog issue. Link to comment Share on other sites More sharing options...
jgcode Posted February 19, 2009 Report Share Posted February 19, 2009 Update: We were able to reproduce this problem, but we're still looking into what happened. We still haven't reproduced the mass compile dialog issue. Although you are on this one, I thought I would mention that the empty palettes happen on my install as well (LV8.5, VIPM 2.0.3). Regards Link to comment Share on other sites More sharing options...
Omar Mussa Posted February 19, 2009 Report Share Posted February 19, 2009 Although you are on this one, I thought I would mention that the empty palettes happen on my install as well (LV8.5, VIPM 2.0.3). Thanks for the feedback. Link to comment Share on other sites More sharing options...
Jim Kring Posted February 19, 2009 Report Share Posted February 19, 2009 I have no idea why this is happening, but I think it might have something to do with the fact that the VIs are members of classes and need to be saved (recompiled) in the newer version of LabVIEW. I've seen this issue, too, but I don't have the exact steps to reproduce. Link to comment Share on other sites More sharing options...
jgcode Posted February 20, 2009 Report Share Posted February 20, 2009 I have no idea why this is happening, but I think it might have something to do with the fact that the VIs are members of classes and need to be saved (recompiled) in the newer version of LabVIEW. I've seen this issue, too, but I don't have the exact steps to reproduce. Additional Info: I mass compiled the VI Test Folder and upon restarting LabVIEW the palettes were refreshed. (I did not uninstall/reinstall like hfettig did to solve it) Regards JG Link to comment Share on other sites More sharing options...
Omar Mussa Posted February 20, 2009 Report Share Posted February 20, 2009 Additional Info: I mass compiled the VI Test Folder and upon restarting LabVIEW the palettes were refreshed. (I did not uninstall/reinstall like hfettig did to solve it) Thanks for the info. You can mass compile the code easily by simply opening the VI Tester GUI -- it will then mass compile all of the VI Tester code. If you then restart LabVIEW as suggested, the palettes should be refreshed as you point out here. We will continue to look into this issue. Link to comment Share on other sites More sharing options...
jgcode Posted February 22, 2009 Report Share Posted February 22, 2009 Thanks for the info. You can mass compile the code easily by simply opening the VI Tester GUI -- it will then mass compile all of the VI Tester code. If you then restart LabVIEW as suggested, the palettes should be refreshed as you point out here. We will continue to look into this issue. Thanks Omar, I wanted to confirm the mass compile fixed the palettes so I did it manually. After that I tested 3 other installs and the automatic mass compile solved the issue as mentioned above. Regards JG Link to comment Share on other sites More sharing options...
Jim Kring Posted February 23, 2009 Report Share Posted February 23, 2009 FYI - I've submitted this bug to NI. I'll keep you all posted with any information I get back from them. Link to comment Share on other sites More sharing options...
Jim Kring Posted February 23, 2009 Report Share Posted February 23, 2009 FYI - I've submitted this bug to NI. I'll keep you all posted with any information I get back from them. NI returned CAR# 148158 for this issue. I'll let you all know when the status changes. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.