Starware - A new concept ?

[parthabe]

Latest link to the download page of the Code Capture Tool.

[muks]

Thanks for the link partha

[parthabe]

Where can I get the CCT for LV 8.0, LV 8.2 & LV 8.5 ?

[tst]

Just use the one from the download page. It says 8.6, but I'm pretty sure that's a mistake and it should work with every version from 7.0 and up. It even compiles itself at the end of the installation.

[muks]

Tst is right. Atleast it works for lv 8.0

[TCPlomp]

Just to keep people updated version 2.0.5 has been released of the Code Capture Tool, including VI Snippet creation, writing comments and drawing on the captured image.

Ton

[chilly_charly]

---

chilly charly a écrit :
The attached starware finds the version of a freshly opened vi. May be that will decrease the number of not-the-right-version posts.[...]

---

In LabVIEW 2010, the source LV version of a VI can be read in the VI properties -> General. No need anymore to go one step further and open the "List of unsaved changes...". Still I find this as a constraint and I would prefer a solution such as the one proposed here.

Meanwhile, here is a new version of the VI version utility, that works in the background once launched. When the vi version does not correspond to the LabVIEW version, it adds a temporary string in all the opened vi's documentation. Hovering the mouse pointer over the vi icon shows the info in the context help window. This string is removed once the vi has been saved in the running LabVIEW version so it will not affect definitively the documentation. Quick and clean...

Unzip the attached file and drop VI version Info.vi and the associated _VI version Info folder into the Project folder (inside the LabVIEW application folder) and restart LabVIEW. A new sub-menu (VI version Info...) will appear in the Tool menu. Call this menu and launch (or abort) the vi. That's all.

I have been using this utility in LV9 and LV10 during the last week without problem. It should work also in LV 8.x, but I'm to lazy to save it in a n-2 version but I have tested it only in LV 8.6 (MacOS). The memory and processor power footprints are negligible. 

Enjoy...

[tst]

You can probably simplify its use even more by adding the string to the FP's title. This way it would be visible as long as the VI is open.

[chilly_charly]

---

tst a écrit :

You can probably simplify its use even more by adding the string to the FP's title. This way it would be visible as long as the VI is open.

---

This was the first option I tried. I was not pleased with the result. Don't remember exactly why. I'll do another attempt...

[chilly_charly]

Now  I know why I didn't like to add the version number in the title bar : the VI name is duplicated.

Anyway, here is a modified version for those who would like to try it, and give their opinion ! 🙂