Old Value & New Value in Property Node

[parthabe]

Hi All,

How about the Property Node itself giving out one more property, the Old Value, along with the New Value [just a caption change instead of the current Value property... ?!

I m in great need of this feature so as to avoid the usage of Event Structure just for those variables at so many places in my code.

Can the veterans explore the more usefulness of the above feature from a wider perspective ?

[altenbach]

To me, "old value" only makes sense in the context of a "value change" event.

Can you explain a scenario where your idea would be useful?

Value property nodes are very inefficient anyway. Just use the terminal and a feedback node, for example.

[parthabe]

It is a huge project wherein some decisions need to be taken based on the result of a particular test [Pass/Fail]. If it fails, it ll be put into Bin5. Likewise many other tests may also be assigned to Bin5 on Fail. So, whenever Bin5 gets incremented, some other processes, as I said earlier, must not be carried out. So, I need to check this BIn5's value in every test execution cycle.

I think we ve got only 2 methods to code for this. Either use a dummy variable to keep Bin5's previous value or use the ES to get its previous value. Then, we can do the comparison with its current value & if there is a difference. I ll avoid doing those processes.

It is a huge VI, wherein all the processes are carried out in the main Producer while loop and the menu pop-ups for datalog & report viewing are done by the consumer while loop. No ES is beibg used as of now.

Does this shed more light on the need ?

Please clarify me about some other methods.

[pincpanter]

Replace bin5 with an Action Engine that does the proper processing.

[Yi Y]

Hi Partha,
Please go to www.ni.com/contact where you can let us know about your product suggestion.
Thanks!

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support