The excution order of accessing to multiple attribute by Property node

[Mars Su]

Hello everyone,

Here I am again.

It a question regarding the property node.

In the book "LabVIEW Graphical Programming, Fourth Edition " by Gary W. Johnson and Richard Jennigs, it's written that: Each item in the list can be either a read or a write, and execution order is sequential from top to bottom.

But I implement an example with multiple access to property node, the data flow of course runs parallel to and reachs the property node simultaneously. So for me it seems that the execution order is not sequential from top to down but parallel. (And this is consistent to the underlying principle of Labview, a data flow language.)

With great respect to the authors, I think I may misunderstand the meaning of the book. Or is it possible that the property node does excute all the accessing parallel?

Best regards

[Grampa_of_Oliva_n_Eden]

Hello everyone,

Here I am again.

It a question regarding the property node.

In the book "LabVIEW Graphical Programming, Fourth Edition " by Gary W. Johnson and Richard Jennigs, it's written that: Each item in the list can be either a read or a write, and execution order is sequential from top to bottom.

But I implement an example with multiple access to property node, the data flow of course runs parallel to and reachs the property node simultaneously. So for me it seems that the execution order is not sequential from top to down but parallel. (And this is consistent to the underlying principle of Labview, a data flow language.)

With great respect to the authors, I think I may misunderstand the meaning of the book. Or is it possible that the property node does excute all the accessing parallel?

Best regards

When you have a property node re-sized for multiple inputs , yes the required data may arrive at different times but one they are all there, the execution is from top to bottom, unless there is an error...

Ben

[crossrulz]

Multiple property nodes will execute in parallel. What the authors are talking about is when a single property node is used to set/get multiple properties (the property node can be expanded just like the build array or bundle/unbundle cluster). Hopefully this picture will help clear things up.

[Yair]

And to clarify it even more - the value of the control will be 6 when the code finishes executing, because the second property executes last, even though it got the value first:

[Mars Su]

And to clarify it even more - the value of the control will be 6 when the code finishes executing, because the second property executes last, even though it got the value first:

Thanks for your great paradiagm.

[Mars Su]

You can't believe this. I meet exactly a question on this topic in my CLAD test. Thanks again for you guys' help.