LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
MorganHero

Clear all retained wires

Status: Duplicate

Use case:

I have multiple (sub)vi's open or in memory with "Retain Wire Values" enabled, because I don't know in advance which wires I need to probe.

 

Initial State: 
If I probe any wire now, they will all show "Not Executed".

 

First Execution:

After I have run my code, these (sub)vi's will show their values as promised and the parts of the code that have not been executed will display "Not Executed". 

 

Now I have learned from my first execution and I made some changes in my code.

 

Second Execution:

If I would run for the second time now, I'll expect that my code will behave differently. This can mean that some code that did run in the First Execution did not run in the Second Execution and therefore would retain the wire values from the first run. In such a case I am not able to tell if a wire value is from the Second Run or from a First Run and actually "Not Executed" in the Second Run.


Normally, I will Disable and then Enable the "Retain Wire Values" option to clear the wire values, but this can be quite a hustle if you have a lot of vi's with this function enabled.

 

My wish:

I would like to have some kind of "Clear all retained wires" button or something that put all my vi's in memory with "Retain Wire Values" enabled in the Inital State, so they will all show "Not Executed" when probed.

 

This seems a simple and effective solution to me.

4 Comments
Christina_R
Active Participant
Status changed to: Duplicate
 

Christina Rogers
Principal Product Owner, LabVIEW R&D
MorganHero
Member

I don't know what NI's criteria are for marking an idea as a duplicate, but in my humble opinion there is a big difference between my idea and the duplicates.

 

The other ideas refer to a single probe, which has to be reset individually, while my idea is about resetting all vi's where the "Retain Wire Values" button is enabled.

 

But still, I don't mind the path, I only care about the destination. If the status change to "Duplication" means there will be a bigger change for implementation of my idea, I will be happy.

AristosQueue (NI)
NI Employee (retired)

If we were going to do any work in this area, we'd be considering all the relevant use cases. When we work on an idea, we have a list of all the duplicates of it to give us an idea of the breadth of use cases and variations in fixes proposed. It's rare that we decide one small slice of a problem is worth fixing while leaving the wider case unfixed. In this case, there's a general problem that there's no way to reset probes to the "never been run" state. However we do that, we need something that can select one, all, or subset, and possibly triggered on event. Thus the duplication among these ideas.