Access directly to Cluster on Front Panel inside other control

[rock_31]

Hi All,

I want to update and access directly to the Value of Cluster on the Front Panel of my VI using Reference, and Ctrl Set Value.

But my Cluster (CONTROL 1) is inside and other cluster and inside Control Tab , so "Ctrl set" function can't find the name of my Cluster .

How can i proceed ? I'm not familiar with Reference Control .

I have attached an extract of my VI .

[jwscs]

try to use a property node directly for the control/indicator

[James_W]

Try this,

You can modularise it a lot more than this.

Essentially you need to drill down through the structure to find the control you want.

You could create your own front panel search for control VI function and use the "Set control values by index" function to do it too.

(depending on how many controls, you might try getting control values by index and seeing if you can use that to scan the FP with a variant conversion?)

James

[James_W]

---

@jwscs wrote:

try to use a property node directly for the control/indicator

---

Well there is also the easy way too is you don't want to run headerless and have something that might be re-usable!

[paul_cardinale]

I can't find a clean solution, but this works:

[rock_31]

Do you have the LV 2010 version of your file ?

[James_W]

so there we have it!

The clean solution. - but very specific.

The generic solution - but you need to know your specific tree.

The midway solution - but it uses VI scripting, and therefore might not work in the runtime environment. (I think that is why I use the approach I do, but it could just be habit.)

[James_W · Accepted solution]

Saved back to 8.6 in case anyone wants to see earlier

[rock_31]

Thx all for your help, 

It's seems like i don't have other choice than do a loop and compare one by one each control with the control i want to find ?

Humm....This is what I would like to avoid....I have about 150 controls (Clusters) in my front Panel; so may be, it could take some time to do that ....

[jwscs]

store the reference to the control in a global or something, after you've found it.

then subsequent changes don't need you to loop through all stuff.

[James_W]

Depends on how you have them arranged.

You can tree down quickly using my method.

Bear in mind that each page of a tab control has a different reference to it.

I bet not all 150 clusters are on the same tab page or just on the FP directly. - and I don't expect you need to update them all the same.

Are you trying to update all instances of the same cluster type - if so you might be better to do create initialisation function which gets all the references and allows you to update at runtime a specific one inside an action engine.

You want to think about which bits you want to make parallel, which things you want to make scalable and how fast your code wants to run.

Lots of open references = higher memory, but faster access is you know which is which and you don't need to keep searching for the control.

[Ben]

This old nugget of mine shows how to get at the values of FP objects.

No scripting required, works in exes and can be a starting point to develop code to get at arbitrary FP controls.

It would be hard to get any more obfuscated than that code.

But it works, and does not rely on any new fangled gizmos.

Ben