LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
LukeASomers

Search for calls of a VI filtered by constant argument

Status: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined. 

I want to be able to search for calls of a particular VI, filtered by argument. This filter would treat any argument wired to something other than a control or block diagram constant as 'unknown'. You would only  be offered filters on things that can be simply represented in one text box (boolean, enum, int, float). I can imagine that ranges would be nice to exclude or require, but just single values would be very nice.

 

This is mainly useful for commands being passed into Action Engines or Functional Globals, but I can see other uses.

 

EXAMPLE:

 

I have a 'Settings FG' vi with an enum 'Action' argument.

 

I go to its icon in upper right, pull down, and pick 'Find All Instances'. There are many, many results, so I want to filter. Since there's only one argument that's not a cluster or an array, I only have one argument I can fill in. I pull down 'require value' for the filter on the 'Action' argument, and pick 'write' as the value to require. The list immediately shortens to a small number of cases.

 

On second thought, I select 'exclude value' as the filter and pick 'read'. A few more cases appear - those must be the 'reset' cases.

 

I check the 'include unknowns' checkbox so that on the off chance that I ever calculated the action to take, it would be in the list. Unsurprisingly, nothing else pops up.

 

3 Comments
P@Anand
Trusted Enthusiast

In my opinion this seems to be a more specific requirement than a normal usable case. The case you explained looks like a FGV and the idea seems to fit only this. When you go for a LV global variable this Write and Read is already displayed (but not filtered). Also writing an algorithm based on the input wiring seems a big effort compared to the time it saves and the usage.

-----

The best solution is the one you find it by yourself
Darren
Proven Zealot

Your best workaround today would be to write a custom VI Analyzer test that detects this specific wiring of your VI across your codebase. 

 

You can use the Find VI Calls test available on the VI Analyzer Enthusiasts community as a starting point.

Darren
Proven Zealot
Status changed to: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined.