LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

One Button Dialog - Stupid Questoin

Solved!
Go to solution

I did a stupid thing.  I put a one button dialog in one of my VIs that Pop-Ups with the word "test".  Test was a poor choice of words, because that string exists like a million times in my program.  Usually, I include a call trace string in by debugging pop-ups, you know... so i don't loose them..

 

Is there a way to find all the VI's the call the One Button Dialog?  If I recall, it's not really a VI, but a yellow/orange function.  For the life of me, I'm not seeing it in dependencies (which if it's a function and not a VI... ).  I'm slowly going crazy looking at all the instances of the word "test".  I'm hoping it's searchable in dependencies, and I'm just missing it.

 

Am I missing something?  If nothing else, have a good laugh at my expense 🙂

0 Kudos
Message 1 of 7
(312 Views)
Solution
Accepted by wldgoose

To find all instances of an object (primitive function or subVI) in all diagrams of your project:

 

1. Open your top-level VI(s) (this allows to load the entire call hierarchy).

2. Press Ctrl+F.

3. Search for: "Objects".

4. Application Instance: usually "<your_project>/My Computer".

5. Select Object: <your_object> (example: Functions > Dialog and User Interface > One Btn Dialog).

6. Search Scope: <All VIs in Application Instance>.

7. Check "Ignore VIs in vi.lib".

8. Press "Find".

 

Regards,

Raphaël.

Message 2 of 7
(303 Views)

One Btn Dialog

 

didn't think to abbreviate

 

My top-level is actually very small.  Most of the application is dynamically opened (which this will miss).

 

 

Still haven't found it, but this was exactly what i was looking for..  if I can't get it w/ this, i'll do some VI scripting..  ugghhh

 


@raphschru wrote:

To find all instances of an object (primitive function or subVI) in all diagrams of your project:

 

1. Open your top-level VI(s) (this allows to load the entire call hierarchy).

2. Press Ctrl+F.

3. Search for: "Objects".

4. Application Instance: usually "<your_project>/My Computer".

5. Select Object: <your_object> (example: Functions > Dialog and User Interface > One Btn Dialog).

6. Search Scope: <All VIs in Application Instance>.

7. Check "Ignore VIs in vi.lib".

8. Press "Find".

 

Regards,

Raphaël.


 

0 Kudos
Message 3 of 7
(288 Views)

Ah, I should have said "Top-level VI(s) and dynamically linked VIs".

 

When I dynamically call VIs that are known at edit time, I usually put a static reference on the diagram next to the Open VI Reference. This forces a static linkage that loads the call hierarchy when the top-level VI is loaded, and it also auto-includes the VI in builds.

0 Kudos
Message 4 of 7
(250 Views)
Solution
Accepted by wldgoose

@wldgoose wrote:

 

Still haven't found it, but this was exactly what i was looking for..  if I can't get it w/ this, i'll do some VI scripting..  ugghhh

I already wrote the scripting code for you. 🙂 Check out this VI Analyzer test:

Test - Find Function - NI Community

Message 5 of 7
(244 Views)

@wldgoose wrote:

My top-level is actually very small.  Most of the application is dynamically opened (which this will miss).

Still haven't found it, but this was exactly what i was looking for..  if I can't get it w/ this, i'll do some VI scripting..  ugghhh



In the old days there was advice to use a "Tree VI" to hold all the top level VIs and dynamic loaded VIs. The "Tree VI" may be broken and is not used anywhere, it is just to load all VI hierarchy into memory if needed and can be used to document call hierarchies and other things.

Searching for an object in a "Tree VI" should find your all your objects.

0 Kudos
Message 6 of 7
(84 Views)

Select the One Button Dialog (drop it in an empty diagram if you don't know of any), Ctrl-F and it should automatically be in Find this object mode.

Yamaeda_0-1779796094187.png

 

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Message 7 of 7
(72 Views)