"Temporary breakpoint" or "Run to here"

[MGiacomet]

When debugging, sometimes you may inadvertently and unnecessarily step into a while/foor loop. Would be nice to be able to let the debugger run that loop and stop just after exiting it. Currently you have to set a breakpoint, let it run till it hits, the delete that breakpoint.

Most debuggers (in other programming languages) have a "run to here" option, i.e., you put the cursor at a certain location and let the debugger run till there. A new entry in the context menu labeled "Run to here" could do just that. stopping at whatever wire the mouse cursor is hovering at.

[jcarmody]

I do that all the time.  I use ctrl+click on a wire to set/clear a breakpoint.  Also, you can just step out of the loop with this button: 

[X.]

@jcarmody: You still need to turn off highlight and then turn it back on if that's what you are using. "Skip to here" would be nice, but admittedly, it is no big deal to improvise a solution based on a breakpoint, as you described.

[PalleM]

I like the "run to here" part... ofc, before i read jcarmody's post, i didnt know about ctrl-click 

edit:  awww, you have to be in run-mode for the ctrl-click to work.  I would love the "run to here" to be usable when not in run mode (it would trigger run mode)

[AristosQueue (NI)]

Although I agree this would be good functionality for LV to implement natively, I think you could probably put together a Right Click Framework plugin to do this. Seems worth investigating as a near-term workaround if you do this often.

[Darin.K]

> I think you could probably put together a Right Click Framework plugin to do this

You guys would have to unbreak whatever broke the RCF first.

[AristosQueue (NI)]

I didn't know it was broken.

[Darin.K]

Not saying that anyone from NI would sabotage anything to help QuickDrop's market share , but the backdoor exploited to autostart the RCF stopped working around LV11.  It has basically withered on the vine since then.