Property node for many items

[IanYuan]

Hi,

I am working on a function that after entering the password, some items will change from "Disable and gray out" to "Enable".

The problem is, when there are many items, I'll have to create property nodes for each of them. As picture below.

It takes a lot of time and also make the block diagram a mess.

Is there any more efficient way to do this work? 

[PalanivelThiruvenkadam]

How about using Control reference and using the Same on need basis for Enable and Disable in a Loop for same type?

[Andrey_Dmitriev · Accepted solution]

You can iterate over multiple controls or indicators via Front Panel->All Objects[] Property Node.

For example, somethijng like that:

[GerdW]

Hi Ian,

Is there any more efficient way to do this work? 

Well in nearly every programming language this rule is true:

When you want to repeat the same operation multiple times you should place that operation in a loop!

With LabVIEW you alos get autoindexing loop, that run very efficiently on array inputs…

[GerdW]

Is there any more efficient way to do this work? 

Well in nearly every programming language this rule is true:

When you want to repeat the same operation multiple times you should place that operation in a loop!

With LabVIEW you alos get autoindexing loop, that run very efficiently on array inputs…

[IanYuan]

Hi, 

I have tried Andrey's sample code and it's working great, thanks a lot!

But can I change the specific items in this way?

For example, if I'm going to change the setting for Boolean 1-3 but not Boolean 4-6, is it possible?

[GerdW]

Hi Ian,

sure!

First read the label of the fp element, then decide what to do based on the label…

[IanYuan]

Hi GerdW,

It's exactly what I'm looking for, really appreciate it!

Enclosed my code if anyone may need it in the future 

[Yamaeda]

Place them in a Cluster and disable/enable the cluster. 🙂

/Y

[Intaris]

Put the disabled control outside of the loop and wire in the value. Just nitpicking.

If your code only ever accesses the same controls, you can cache the control references on first execution to speed things up a little.

If you do things in a sub-VI, the caching can still be done if you choose "Re-entrant - preallocated clones". And here, if all the VI does is write to property nodes, you might also shave off some time by setting the execution thread of the sub-VI to "UI Thread".