Disable/Enable debugging for all vi's in project

[Taylorh140]

The question is quite simple. Is there a way to globally enable and disable debugging. I know there is a slight performance penalty for having it enabled, and I'm trying to figure out how much performance i can squeeze out of my algorithm. It would be nice if i didn't have to go into each individual vi and toggle this setting.

[tyk007 · Accepted solution]

There is no simple way in the IDE to accomplish this purely for development purposes. If you are creating a build specification (executable, source distribution etc.) then you can adjust this for the distribution itself so that the "build" has debugging disabled. You can also script a simple VI to go through and programtically modify this setting on a group of VIs.

[Hooovahh]

If you are looking for performance improvement, you may also be interested in turning off the automatic error handling.  This can also be done for a batch of VIs using VI scripting.  But if you are having performance issues, don't expect this to fix all of your problems, the overhead in most cases is very small.

[Yamaeda]

If squeezing performance from a few algorithm VIs you can change their priority to Very high or Real time.

Though, is the code decent to start with, or are you putting make-up on a pig?

/Y

[Hooovahh]

---

@Yamaeda wrote:

Though, is the code decent to start with, or are you putting make-up on a pig?

---

This is what I suspect.  Also there is a private method for determining if a VI can be inlined.  Of course it doesn't detect things like Call Chain, and uninitialized shift registers, which are functions that can be inlined, but can behave differently.  

Our internal reuse library has a pre-build VI that gets ran which turns off automatic error handling, and debugging (among a few other features).  This library has also gone through an audit process finding VIs that can be inlined.  It is a little annoying to have to change those settings back when debugging some odd behavior but the idea is that reuse shouldn't need to be debugged, it should just work.  I guess that's not always the case.