"Retain Wire Values" Issue

[Mr._Bob]

Recommend that the “retain wire values” feature continue to retain the values EVEN AFTER the program pauses, errors-out, stops, or is aborted by the programmer. What good is it if the program stops and you can’t probe the history? The system was maintaining the values up to that point anyway. There should be no reason why those values cannot be retained in memory after a stoppage, at least until someone attempts to make a change to the program.

I determined that a workaround for this issue is to create a separate while loop the never stops. Then, when the program comes out of the main loop with an error, the separate while loop keeps the program running so you can see all the retained values. Naturally, lines that did not execute have no line info.

Bob
 

[iannicholson]

It's a shame I was a couple months late to this...

I like the way the tip-strip shows the value while you are paused. It acts like a sort of real-time probe. Frankly, the probe interface (even the new one) is quite cumbersome, and the ability to mouse-over any wire and instantly see its current value is fantastic. Using the probe windows requires multiple clicks and mouse movements, which distract from the actual debugging.

Please don't remove the tip-strip probing, or at least replace it with something even easier to use/understand!