You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are quite a few things indicated in data point properties, some of them are more or less duplicate.
Example 1 : there is the "scientific unit" field, but also, if we select analog formatting, the suffix which naturally contains the unit. By the way, what is the current actual use of the "scientific unit" field ?
Example 2 : the tolerance used for data recording, when used, will most probably match the analog format : if one choses to display a number as #,###.#, there is a high probability that 0.1 would be a meaningful tolerance for data storage.
if a scientific unit is selected, then the analog format should be automatically pre-selected, and the suffix should be filled with the appropriate short version of the unit
once an number format is chosen (#.# for example), then the tolerance should be filled with the matching precision (so 0.1 in this case)
the block "text renderer properties" should be placed between the "point property" and the "logging properties" blocks. It would then also make sense to keep "chart rendered properties" close to "text renderer properties".
why is the "purge after X years" not included in the "system settings" ? Or at least a general default value should be part of system settings, and could be modified case by case for each datapoint ?
The text was updated successfully, but these errors were encountered:
Additional idea : we could also imagine a way to configure that, by default, a measurement point in volts is stored X years with a precision of 0.1 and displayed as #.# with suffix V, and so on for each any unit. This would save a lot of time during the configuration of new datapoints.
- Now changing engineeringUnits is Point Properties view will change its suffix to the according one
- Now changing number format in text renderer will automatically change tolerance in logging properties of the point
- Added attribute 'unitsMap' to 'engineeringUnits' tag, and refactoring generate select;
- Created enums EngineeringUnitsTypes, created class EngineeringUnitJson for serialize units, and created interface EngineeringUnit;
- Added test: EngineeringUnitsTypesTest;
- Removed method: DataPointEditDwr.getEngineeringUnitSuffix;
- In DataPointEditController.showForm and DataPointEditController.saveDataPoint added attributes: unitsMap, unitsListJson;
- Refactor function updateSuffixForEngineeringUnits in dataPointEdit.jsp, added set value for fields: textRendererPlainSuffix and textRendererAnalogFormat;
There are quite a few things indicated in data point properties, some of them are more or less duplicate.
Example 1 : there is the "scientific unit" field, but also, if we select analog formatting, the suffix which naturally contains the unit. By the way, what is the current actual use of the "scientific unit" field ?
Example 2 : the tolerance used for data recording, when used, will most probably match the analog format : if one choses to display a number as #,###.#, there is a high probability that 0.1 would be a meaningful tolerance for data storage.
The text was updated successfully, but these errors were encountered: