Implicit wait for "run continuously"

[altenbach]

The "Run Continously" tools is typically used as a debugging tool to quickly play with inputs for "pure" subVIs that don't have a toplevel while loop (see also my comments here). This sandbox mode has the unwelcome side effect that the computer uses 100% of at least a single CPU core while doing so, starving all other processes that might already run on the computer. It gets even worse if I use "run continuously" on several subVIs at the same time. (Yes, I am a multitasker! :D)

Another use of the continous run button seems to be a certain other class of users. Also in this case, the high CPU use is a serious drawback.

All use scenarios I can think of suffer from this. There is no real advantage to run this fast without taking a breather.

My suggestion (first mentioned elsewhere)  is that there should be an implicit small wait (e.g. 10ms) between each restart so the continuouly running VI behaves more politely and is less demanding of system resources.

[rgvdh@rdf]

If implemented it should be a configurable option.  Maybe one of the "execution" properties in "VI properties"?

People doing debugging might want 10ms.

People doing benchmarking might want 0.

Someone who's just slapped together something that takes one measurement, needs to take 1000, and then will never use it again might want 10ms, 250ms or 60,000ms. 

For backwards compatibility it should default to 0, but the first time you hit "run continuously" with a delay of "0" you should get an "Are you sure?  This will hog system resources." dialogue and the option to change it.

[SteveChandler]

Would it be possible to add a right click menu to the run continuously button? If so maybe the delay could be set that way. Also the button could change to indicate delay mode is enabled. Something like an hour glass superimposed over it. I am kudoing this on the assumption that the delay is somehow configurable.

[SteveChandler]

Or maybe control click enables the delay?