Probes should reset to 'Not Executed' on Run

[magicbean]

Probes are useful for seeing when a piece of code has executed for the first time after clicking 'run' as well as to see real-time values on wires.

Currently probes retain their values when the top VI stops, which is useful, but less usefully, keep their values indefinitely, even when the VI is restarted.

I'd like them to reset to 'Not Executed' when you click 'Run' again, otherwise I have to delete and recreate each probe in order so that I can tell when they have executed for the first time (unlike the lightbulb which slows everything down, breakpoints which pause the code or adding indicators which may not be convenient on a front panel (and require initialisation code)).

If this could be implemented (or could be an option for all probes or for any individually by right-clicking on them) I would find it really useful!

[magicbean]

Perhaps instead of a button at the top of the probe window we could have a checkbox 'Reset on run'. If the checkbox is set, probes are cleared on run, if it's clear, the probes keep their values on run.

[Intaris]

I could go with a button or a checkbox although I could imagine a checkbox being a better solution because as luck will have it that ONE time you forget to manually reset something, you needed that functionality urgently.....

Having said that, I think a button to do a once-off reset is perhaps easier to implement.

[fabric]

Personally I'd prefer a button where the resetting is delinked from the running of the VI. "Reset on Run" seems a little arbitrary to me... I like the idea of being able to reset probes any time I feel like it - maybe multiple times per run.

[Intaris]

Maybe we should just ask for both.....

[LukeASomers]

> I like the idea of being able to reset probes any time I feel like it - maybe multiple times per run.

I approve. Just add 'reset' to the drop-down menu for (multiple) selected probes. Very simple, doesn't get in the way of anything else.

I guess the checkbox for reset-on-restart would also be fine.

[jasn009]

A slightly different take on this - if I add a probe to a wire AFTER the wire has been executed, but before the program terminates, it should show the last data on the wire, not "Not Executed". Right now, if I add a probe to a wire after it's been executed, ii says "not executed".  This is not helpful.

[AristosQueue (NI)]

Jasn009: The feature you're requesting already exists. It's called "Retain Wire Values." There's a button on the block diagram right next to the Execution Highlight button. Click that. Now every wire will retain its last value and you can add probes after they have executed. The Probe Watch Window displays the timestamp of the last execution time.

The trade off is performance drops noticeably in many apps because LV has to retain the data values everywhere, which is why it is an opt-in feature instead of on by default.

See -- not every idea gets rejected. 🙂