From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
When debugging, I often find I need to jump over a number of operations before jumping into an operation I'm interested in. It would be nice if we could mark VIs to not be entered (always skipped) when debugging, so that I can just spam the jump into key until I hit the one I want.
I don't think that is what he is looking for. It sounds to me that he wants the subVI to execute, but wants to have it marked not to be stepped into, but to be stepped over without having to hit the other debugging step button at the right moment.
I'd argue that related or perhaps better ideas are
Well the OP mentioned "VIs to not be entered (always skipped) when debugging"...
Anyway, I can see some value in extending this idea to other structures (and maybe even a "don't debug structure"), but I'm still not sure if I'd really use this much. It would need to be sufficiently quicker and easier than using breakpoints...
Yes, turning off debugging achieves this effect, but it has the side effect of making it so you can't debug those VIs when you actually do need to go into them, and you end up editing the debug settings of the VI. This would allow for a much nicer compromise position, IMHO.
For the record, I would advocate to turn it on by default on every single VI in vi.lib and every shipping toolkit API. Once an API is done, for the most part, there's no value in stepping into it on every function call.