LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Andreas_Pfichner

Breakpoints should not change VI version

Status: New

When adding one or more breakpoints to a VI, the user is asked to save the VI when closing it even in the case that he has already removed the breakpoints again manually or with the breakpoint manager. When using sourcecode control like TortoiseSVN, this makes always trouble when closing a larger batch of VIs and no time to look which VI has been really changed and which not. Because then you will save a new version of a VI which has not been changed at all. You have to click around a lot to not get into these conflicts.

 

Saving breakpoints with a VI might be a helpfull option for some developers (not for me, I have never had the need to save breakpoints with a VI).

 

Nevertheless my suggestion is  that the version status of a VI should not be changed when adding breakpoints, or at least should be reseted when the breakpoints have been removed again.

2 Comments
TCPlomp
Trusted Enthusiast

Without the possibility to save breakpoints with VIs it's very hard to debug reentrant VIs.

 

However your idea is nice, but there are so many things that can cause a VI to become dirty (recompiled), it's quite hard to get this straight

 

Ton

 

 

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Andreas_Pfichner
Member

Hi Ton,

 

saving breakpoint possibility does not to be deleted to handle the things like I have suggested. (Nevertheless for debugging reentrant VIs I use to implement "debugVIs" into the reentrant VIs for probing/conditional breaking).

 

"So many things" cause a VI to become recompiled, you are right, these are for example changed typedefinitions, changed subVIs etc. But in this case the VI really changed and SHOULD become a new version.

 

When you add and remove a breakpoint, the VI, the "code" has NOT changed. In this case it SHOULD NOT become a new version.

 

My suggestion is aimed at distinguishing WHAT changes a VI: the LabView TOOLING or the CODING of the programmer.

 

So I suggest, to get it straight, to distinguish, if the LabView TOOLING "changes" a VI, then it should not be recompiled, or if the VI is changed by CODING.

 

Thank you.

 

Regards

 

Andreas