XControl value change bug when updating value from "Display State

[Jeffrey Habets]

Case: given an XControl that has some custom property. If we write to the property, the facade will be called with the Display State Change event. The XControl determines from the property write that the XControl's data needs to be changed, so it does. (Illustrated in the example by applying the random value to Data Out.)

Now when the VI using the XControl uses a property node where the first property written is a custom property (which as a side-effect induces the value change as described) and the second property is the Value which we write a value to (5 in the example), then when we read the Value-property again after that we would expect to see the value we wrote before (5). Instead we get the value that was induced during writing of the first property (Range in this case).

If we change the example code (see disabled case) to first write the custom property and then write the value property using a separate property-node everything works as expected.

Download File:post-906-1236990414.swf

Download File:post-906-1236987840.zip

[Jeffrey Habets]

This has been registered under CAR# 156392.