Debugging Off

[GraemeJ]

Using VI Analyser from the main vi, I can detect if debugging is on or off in the main vi but not in the sub vi's or the rest of the vi hierarchy.

Is there a way of achieving if debugging is off throughout the whole code, or is it necessary to go through each and every vi? If the latter, this becomes very cumbersome in a large project.

Regards, GraemeJ

[crelf]

QUOTE (GraemeJ @ Aug 2 2008, 08:13 PM)

Is there a way of achieving if debugging is off throughout the whole code, or is it necessary to go through each and every vi? If the latter, this becomes very cumbersome in a large project.

I'm sure there'd have to be a scripting node that reads that for each VI, and then you could do some Boolean logic (sorry, a bit flat out at the mo, otherwise I'd try it for you...)

[Darren]

QUOTE (GraemeJ @ Aug 2 2008, 07:13 PM)

Using VI Analyser from the main vi, I can detect if debugging is on or off in the main vi but not in the sub vi's or the rest of the vi hierarchy.

Is there a way of achieving if debugging is off throughout the whole code, or is it necessary to go through each and every vi? If the latter, this becomes very cumbersome in a large project.

Typically your entire application resides in a folder structure of some sort on disk. Can you just create a new VI Analyzer task (as opposed to using the "Analyze this VI" functionality) and add the folder(s) containing your app, then run the Enabled Debugging test over the entire folder?

-D

[LAVA 1.0 Content]

QUOTE (crelf @ Aug 3 2008, 02:39 AM)

I'm sure there'd have to be a scripting node that reads that for each VI.

Don't think to easy for LabVIEW, debugging is just a normal VI property node.

OpenG can return all the VIs called by another VI, shouldn't be too hard.

Ton

[Val Brown]

QUOTE (Ton @ Aug 2 2008, 11:06 PM)

Don't think to easy for LabVIEW, debugging is just a normal VI property node.

can return all the VIs called by another VI, shouldn't be too hard.

Ton

OK, any suggestions for implementing that same code without using OpenG? I know that's probably almost sacriligious here but there are some of us who don't use OpenG.

[crelf]

QUOTE (Val Brown @ Aug 3 2008, 05:34 AM)

I know that's probably almost sacriligious here but there are some of us who don't use OpenG.

Off topic alert: Why don't you use OpenG? Maybe we should break this into a separate thread...

[Yair]

QUOTE (Val Brown @ Aug 3 2008, 12:34 PM)

OK, any suggestions for implementing that same code without using OpenG?

You need to use the Callees[] property of the VIs until there are no more VIs which you haven't listed. One way would be to have two arrays (VIs which you already went over and VIs which you haven't went over yet) and to make sure that you have no duplicates.

[LAVA 1.0 Content]

QUOTE (Val Brown @ Aug 3 2008, 11:34 AM)

OK, any suggestions for implementing that same code without using OpenG? I know that's probably almost sacriligious here but there are some of us who don't use OpenG.

QUOTE (crelf @ Aug 3 2008, 03:25 PM)

Off topic alert: Why don't you use OpenG?

Maybe we should break this into a separate thread...

Interesting discussion, but I think it will be a company guideline thing. (If Val wasn't open to others people code, he wouldn't have asked)

Here's a very rude example:

Ton