Easy way to work with array of control references?

[jcarmody]

You might be able to "tag" a control and find it by that.

First run:

Change names and order of controls in cluster (and disable the tag-setting loop):

I still got the same tag values for the controls with the original tag names.  Name and order don't matter any more.

[dems]

It sounds like you both understand my point and don't understand my point. On the idea exchange one of the suggested workarounds was getting a ref to the control you want to modify inside the cluster. That is, if you want to modify the boolean in slot 2 you get a reference to it. Yes, managing 20 of these individual references when LabVIEW has the info you need to make it easier on you is annoying, but you said safety was your priority. This seems like the way to do it.

[jcarmody]

---

@1984 wrote:

[...]

If I change the order of the elements in the cluster then the order in the controls[] array will change as well and that can remain completly hidden. So referring to the controls by their index in the controls[] array is not optimal. Also referring the control by their name isnt optimal as you may change the name of the items after a while.

[...]

---

I've seen  instances where changing names/order in clusters isn't handled well by the editor and the unbundle nodes end up broken (or worse, if the same type is unbundled and nothing breaks except functionality).  I expect the same would/could happen if we could unbundle references the way I think you want.