LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Search not finding stuff

So, working on a very old project that's been upgraded through LV versions and generations it has some strange behaviors:

When searching for text in order to fix some problem nothing is found. If i open a vi and search only inside the vi, not the project, it's found.

(It exists as a dependency in the project)

 

Any ideas as to why it behaves like this?

 

/Y

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 1 of 5
(2,691 Views)

In order to search for text within a VI the VI must be in memory, therefore make sure you open the top-level VI of your project which will cause LabVIEW to load all dependencies into memory. Point the search utility to this top-level VI in the Search Scope and ensure SubVIs is checked. This should effectively search within all directly called subVIs.

 

If your codes are being called dynamically through VI Server then these VIs will not be in memory and you will need to manually open them to ensure they are searchable. In this instance set the Search Scope to <all VIs in Application Instance> to ensure they are part of the search.

Thoric (CLA, CLED, CTD and LabVIEW Champion)


0 Kudos
Message 2 of 5
(2,665 Views)
It's an old program, all is directly linked from Main, no dynamics. The project is basically the main vi, the rest is dependencies. It do, e.g. Find my clusters with a text, but it doesnt find it in string constants and bundle/unbundle.
I think this wad originally lv2-code.
/Y
G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 3 of 5
(2,654 Views)

On several VI's, is i edit the icon, the new layered one immediatly closes and i get the old one.

/Y

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 4 of 5
(2,632 Views)

It sounds like there are some issue with the VIs.

It might be worth conducting a full recompile of the entire hierarchy. To do that, open the top-level VI and press CTRL+SHIFT+Run Arrow, this will cause a recompile of the top-level VI and all called dependencies. Remember to perform a save all afterwards!

Thoric (CLA, CLED, CTD and LabVIEW Champion)


0 Kudos
Message 5 of 5
(2,618 Views)