11-07-2013 03:42 PM
@ToeCutter wrote:
Dude, it's not complex to read the LabVIEW help on property nodes.
Right click on your 'm' value on the diagram, select 'create->property node', right click it and select 'change to write', and use the little hand tool to select the property 'value' on it. Then wire it to the output of your right hand block.
haha sorry about that
but i mean i never used property node before
it solved
thank you to alll
with kuds
11-08-2013 06:29 AM - edited 11-08-2013 06:31 AM
@ToeCutter wrote:
You could change the original array by creating a property node linked to its value and connecting it where your arrow is.
Why a property node? Using the Value property is just like using a local variable except it is incredibly SLOWER.
That array should be an indicator since only the program is updating it. Secondly, the count array should be stored in a shift register. By using a shift register and the terminal of the indicator, no property node or local variable is needed. And this is the perfect place for an In Place Element Structure.
11-08-2013 06:42 AM
"Using the Value property is just like using a local variable except it is incredibly SLOWER."
Thanks. That's news to me. Why is that?
11-08-2013 06:50 AM
@ToeCutter wrote:
"Using the Value property is just like using a local variable except it is incredibly SLOWER."
Thanks. That's news to me. Why is that?
Using a property node still opens you up to the race condition issues as a local variable. So it has no benefit over the local. But the property node is a lot slower since it has to go through more hoops as well as swap to the UI thread. Thread swapping is very expensive.
11-08-2013 07:59 AM
Thanks for the info.