LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Option to Separate Breakpoints from Source Code

Status: Duplicate

Breakpoints are great for debugging.  But...I've never wanted to share them with another developer, and I've never liked it when they add the dirty dot to code that I haven't otherwise changed.  This can lead to unnecessary code changes which can add hassle to source control, and it can lead to other developers unintentionally inheriting your debugging breakpoints.


How about an option to manage breakpoints separately from source code, perhaps similar to how compiled code is handled?

Active Participant

My last team hated when I checked in code with breakpoints added. I thought of adding a pre-commit hook to look for breakpoints before allowing commit to SCC but never got to it. I would have liked this feature. Now I'm a single developer and don't need it, but it would still be good to be able to separate breakpoint change from real code change.

Certified LabVIEW Architect
Active Participant
Status changed to: Duplicate

Christina Rogers
Product Owner, LabVIEW R&D