Use "In Place Element Structure" for VIs for Data Member Access (lvclass)

[TapSch]

To achieve better performance and efficiency, the “In Place Element Structure” should be used instead of the “Bundle by Name” method for “VIs for Data Member Access” (specifically for write VIs). The "Mark as Modifier" option should also be activated.

If the compiler optimization can do this automatically, I apologize for this post. 

[crossrulz]

1. I'm pretty certain the compiler makes those two equivalent.

2. I think you are misunderstanding the point of the Idea Exchange. The reason for the Idea Exchange is to tell NI features/changes we want to see in the LabVIEW IDE.

[TapSch]

1. Ok than I apologize for this post. 

2. If you work with lvclass you are able to build this VI for Data Member Access automatically. So I think it is a feature/change for LabVIEW IDE.

[wiebe@CARYA]

The IPE is only potentially more efficient if you actually read, modify and write (clusters, array elements, variant attributes, etc).

If you only write the value, the IPE is not going to be more efficient.

The hole point of the IPE is that the read value is modified, in place, to avoid a copy.

[Christina_R]

For simple read/write accessor VIs, there is no performance benefit to using the In Place Element Structure. You can choose to use the structure in situations where your accessor VI is performing more complex operations. NI R&D sees no benefit in adding the structure to the default template when the overwhelming majority of accessors are performing simple bundle/unbundle operations.