The current data handling of ao Records is odd when the OROC field is set:
The record is processed twice, because of the dataChange callback after set a value. So the OROC value is applied twice!
This causes the VAL field to be changed to the current OVAL field. That is not what we want!
My suggestion is to introduce a flag in the uaItem that prevents from processing in the dataChange callback. This could be used to switch off the readback behaviour of out records set by info-field and should be set as long as a record is about to in-, decrease its value.
The current data handling of ao Records is odd when the OROC field is set:
The record is processed twice, because of the dataChange callback after set a value. So the OROC value is applied twice!
This causes the VAL field to be changed to the current OVAL field. That is not what we want!
My suggestion is to introduce a flag in the uaItem that prevents from processing in the dataChange callback. This could be used to switch off the readback behaviour of out records set by info-field and should be set as long as a record is about to in-, decrease its value.