Bug in VI Analyzer 2010 support Files stop the creation a Quick Launch solution

[danny_t]

Hi,

This issue is a pain for me as we have just completed our full transition over to LabVIEW 2010.  I am sure that I raised this as a problem in the 2010 Beta Testing and was given a new VI to solve it, but it appears to still be a problem in the released version and the beta forums have long gone.

The guidelines to to create a Quick Launch VI analyzer test involves the use of the VI  VIAnUtil Check If Valid Menu Launched VI.vi  

In previous version of the VI Analyzer toolkit this VI had no input, however in the 2010 version of the toolkit it now as a required input VI Path and thus error if you try to use it from the Tools Menu.

The VI is part  the  \LabVIEW 2010\vi.lib\addons\analyzer\_analyzerutils.llb library is password protected so I cannot fix the problem myself. I suppose I could throw the LabVIEW 8.2.1 version in the the lib, but I would rather have a proper Vi or better yet a new _analyzerutils.llb from NI.

Should I raise a CAR on this issue or is out of scope as it is not a VI provided in the palette

cheers

DannyT

[Darren · Accepted solution]

In LabVIEW 8.5 and earlier, Quick Launch VIs were launched from the Tools menu through the built-in mechanism of placing the VI somewhere in the [LabVIEW]\project folder.  In LabVIEW 8.6 and later, we started using a different mechanism to launch Quick Launch VIs related to the fact that the toolkit became licensed.  Specifically, the VI Refnum for the VI from which the menu option was selected is passed directly in to the Quick Launch VI...as long as there is a control called "VI Refnum" somewhere on the panel of your Quick Launch VI, the VI refnum will be passed in, at which point you can do whatever you want with it...but usually, you'll just be passing it in to VIAnUtil Check if Valid Menu Launched VI.vi. 

Can you modify your Quick Launch VI to have the same structure as the Quick Launch template at vi.lib\addons\analyzer\analyzerapi.llb\VIAn Quick Launch VI Template.vit ?

[danny_t]

Darren,

Thank you for your quick reply that is great, I will do that change when I get into work tomorrow morning.

I am having fun with the, create your own tests by the way feature by the way.  I have done one to check the state of the "separate compile code from source code flag, copied from you Debug enabled one, so thank you for leaving a good number of unprotected tests for us to look at.

It would be great if there was a "global" VI Analyzer path somewhere I could set so that I could place my configuration file *.cfg and my own user specified tests within my source control on a server and easily ensure that everyone runs exactly the same VI Analyzer tests as we have the VI Analyzer as a formal part of our code review process.

cheers

Dannyt