how to find where data in a cluster is written

[mersdal]

I have a large application that I've inherited from previous makers, my job is to complete it and bugfix it. it has 729 unique VIs, the main application uses producer-consumer patterns and many functional global variables. 

the alternative would have been to use the actor framework, but since this is 3 years into the development, it is not an option. Also, I would need more training for actor framework.

My question is: how to find where data is written, I want to find something like this :

in words:

I want to find where a specific item in a cluster is being written to. but only this specific cluster. and written to of course. 

the find function does not seem to be able to do this.. 

also searching by name and then by function and corellating this might work ? but its not implemented in labview. 

so what I did: 

copied search results for bundle by name function (508 items. )

copied search results for CSTheta (20 items)

pasted it into excel, and correlated the results, 

the result: 2Vis, 48 values. meaning that I've found the two vis using bundle by name and having CSTheta written in them. 

the rest is grunt work 😞 no ctrl+g anymore. .

anyone have a better method?

[mersdal]

just found a solution:

the "Found In" tab on the search function, shows some text about where it was found. and here it shows "-Diagram, Bundle By Name, Data/Part"

I feel like such a noob. 

[CoastalMaineBird]

The POST THIS QUESTION button sometimes has remarkable problem-solving effects...

;->

[billko]

---

@CoastalMaineBird wrote:

The POST THIS QUESTION button sometimes has remarkable problem-solving effects...

;->

---

I believe it gives you a +50 bonus to your IQ for a period of time which varies proportionately with amount of kudos you've given.  😉

[JÞB]

---

@mersdal wrote:

just found a solution:

the "Found In" tab on the search function, shows some text about where it was found. and here it shows "-Diagram, Bundle By Name, Data/Part"

I feel like such a noob. 

---

That would be one way to get there!  I won't bother posting my screenshots now.

[mikeporter]

You have to admit though that your original solution was -- uh... um.... impressive 

Mike...