Hi, has anybody of you ever seen a feature as described in the post in your environment?
Thank you
Update: As some readers appear to have skimmed the text, please feel free to point out possible accessibility issues, poor choices of words, etc.
Hi, has anybody of you ever seen a feature as described in the post in your environment?
Thank you
Update: As some readers appear to have skimmed the text, please feel free to point out possible accessibility issues, poor choices of words, etc.
Yes, visual studio lets you do this. You can drag the marker on the line of code that it’s paused at, and move it around. There’s probably restrictions, however it works in most simple cases.
A link here indicates that it’s also possible in VS Code, however it may be C#/C++ only.
Visual studio attached to Internet Explorer was able to do this with JavaScript too. I miss that feature in chrome/VSCode.
That is not the feature I described, though. I’m aware of CTRL + SHIFT + F10, but the feature description is basically a simple way to automate setting the next statement.
Be honest: Is there an issue with the representation of the page or did you skip those parts?
It would be handy if I needed it in a loop that was going to repeat many times.
For most cases, I wonder if setting it up would take more time than hitting the brakepoint and moving the pointer manually.
I already rarely use conditional breakpoints for the same reason.
I feel you. It’s annoying how the good stuff for debugging is hidden in some crappy menus in VS and IntelliJ by default.
About detour points: The second and third version shown in my post would be one keystroke. The first one is probably not worth it, unless they could be set in some sort of modal workflow, similar how setting tabbing order works for Windows Forms.
Ah, I see. I didn’t see the bit about it being a breakpoint (detour point?). That’s what I get for skim reading rather than comprehending it. Visual studio will let you do this, but it’s a manual step, by combining a normal breakpoint and an execute next statement, and you’d have to do this each time you hit the breakpoint.
Having it happen automatically? A fairly niche feature, but I can see a few uses for it. The component features are already there, so I don’t think it would be difficult to implement in a debugger that already supported execute next statement.