Community Nugget, 02/27/2008

[JB]

I have discovered this very useful tool some days ago and I would like to thank all the contributors for this new version.

[tst]

Yes, Ton, that's what "later than 6.1" means.
I should probably have said "7.0 and later".

---

Ravens Fan wrote:

It looks like deleting the Code Capture Tool.llb from the c:\Program Files\National Instruments\ LV X.X\Project directory will take care of that?

Yes, that should take care of it. LabVIEW enumerates all the top level VIs in the Project directory when it loads and displays that list in the Tools menu. Deleting that file will stop LabVIEW from doing that. If I remember correctly, all versions of the CCT were either an LLB in the Project directory or a directory in user.lib, so you should be fine.

We thought of deleting older versions of the CCT at some point, but I guess we didn't get around to doing it.

By the way, one additional note - the CCT is not currently very efficient and it makes several copies of the image data. If you have a large block diagram or front panel this can consume a lot of memory. This is something we're aware of, but need to see exactly how to handle. This is only an issue if you attempt to capture a large diagram (e.g. 2000x1500).

[tst]

---

nrp wrote:

Is there a changelog available somewhere?

---

The wiki page has a changelog and known issues section.

The source code is hosted at SourceForge here. I believe that you should be able to check it out and see the revision history with any Subversion client.

[craigc]

Great Tool,

Nice work and congrats to all involved.  One small niggle i had was it turned of the grid alignment on my front panels (Which i just turned back on again).

Thanks

Craig

[tst]

---

craigc wrote:

One small niggle i had was it turned of the grid alignment on my front panels (Which i just turned back on again).

---

It should have done no such thing. Are you sure this was caused by the tool and not by you manually pressing Ctrl+Shift+3?

I just tested it and it did not turn off the alignment. Can you provide an example?

[Gabi1]

Thanks TST and all involved!

really a great tool, that i use quite often already. new version even better.
creating doc info is sooo much easier with it!

[craigc]

Hi tst.

Pretty Sure i did not hit Ctrl-Shift + 3, and not sure i can provide an example.  I can maybe try to Uninstall - re-install and see if it happens again.  All i done was quit Labview, Run the installer, quit LV then open a blank vi and run the capture tool.  Then my blank vi (With grid on) turned the grid off when the capture GUI was loaded.  Kinda odd i know, and i havent had any problems since.  Also the grid was still present untill the screen was updated(hard to explain, moving a window over the top of the vi rubbed out the grid)

I will have a go at a re-install tommorrow to see if i can repeat the effect :).

Again Thanks for the tool!

Craig

[tbob]

First I want to thank all the developers that made this tool possible.

An earlier post stated that wiki page has a list of known issues.  One of these issues is that opening the tool from the Getting Started window (no vi open) caused Labview to crash.  Wiki says that this issue was fixed.  I just tried it using Labview 8.2 and it crashed labview.  So it isn't really fixed.  Of course the solution for now is not to open the tool unless you have an open vi.  But perhaps the developers should look into this minor issue again.  One solution would be to disable the menu selection if there are no vi's open.

Thanx again for the tool guys.

[tst]

It doesn't crash in the current beta. It does throw an error (VI locked), so we should probably detect this error and disable the BD options if the VI is locked. I don't know if that will solve the crash or not.

We can't disable the menu option, since we don't control that.

[tbob]

Here is the exact actions I took to cause the crash:

1.  Open Labview (no VI opened), splash screen is displayed.

2.  From the splash screen, select Tools -> Code Capture Tool

An error message is displayed with a Continue button.

3. Click Continue

CRASSSHHHHHH......  Labview screen is gone, but Task Manager says it is still running.  Everything else on my computer works fine, just no Labview.

4.  I can kill LV from the Task Manager and start it again fine.