There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
The OnChangeAction options can't be used on meters, just on measures. You did use a such option on the [MeterCondCurrent] meter. Instead you could use the OnUpdateAction, which can be used on meters.
And one more: [StringTimestamp] is a meter. There is no reason to use a Text=[StringTimestamp] option in a String meter, because a String meter doesn't have a value which could be displayed by another String meter. Even if the above issue was fixed (so, the OnChangeAction option of the [MeterCondCurrent] meter was replaced with an OnUpdateAction), in the [Timestamp] meter you'll get the Text=[StringTimestamp] option, which is meaningless. In plus, even if it would be used correctly, a such option would require DynamicVariables=1 option, which is missing.
To be honest, for me it's not clear enough so far what you would like to do.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
