"offset" should be TID_DOUBLE, history config page "offset" field too short

Issue #145 resolved
dd1 created an issue

The "offset" field on the history config page is too short for entering high-precision floating point numbers. For example, if the value is "6.25001e+07", I cannot change it to "6.25001987654e+07" - typing "987654" is rejected because the edit field length is fixed and would not grow. K.O.

Comments (4)

  1. dd1 reporter

    "offset" is too short to work with high precision clock frequency values (i.e. 62.5 MHz counted with 1Hz precision).

    Instead of changing it from FLOAT to DOUBLE, I should probably introduce separate offset1 and offset2 variables: y = offset1 + slope*(y-offset2).

    K.O.

  2. dd1 reporter

    values now switched to DOUBLE and migrated to STRING formula. history editor shows entry field for the formula, offset & co editing is done in ODB. K.O.

  3. Log in to comment