See AristosQueue's comment on page 2 for reasoning. Basically, systems would take a huge memory and performance hit to add this functionality. A lot of developers really like this idea so we will continue to look for ways to implement this in a way that wouldn't affect performance. This is not possible in the foreseeable future though (~2 years) so I'm moving this idea to declined for now but it will definitely not be forgotten.
I would like the ability to probe the loop iteration terminal ("i" in For and While Loops) without the need to wire it to something (indicator, edge of structure,...).
The i terminal is the most common use case for this, but this will probably be useful on any unwired output.
The main problem I see with this is that it has some performance implications. Currently, if LabVIEW sees code which has all its outputs unused, it ignores it when compiling the VI. I would say that if this takes too much effort, special code should be written to support just the i terminal as early as possible.
If there are performance issues, it could be off by default and only available if we enable "deep probing" or similar. It could be part of the "retain wire values" option.
Great suggestion. I frequently need to see the value of the loop "i" terminal.
>
"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
