The separate class GtMonitoringProperty and the specific classes GtDoubleMonitoring (and int and string) are not necessary if the abstract property has a flag if it is a monitoring one.
Description
The class GtMonitoringProperty is removed.
The GtAbstractProperty now has a flag for monitoring properties.
The existing usages are replaced by "normal" properties. To reduce the need of code changes a "using" is added to read e.g. GtDoubleMonitoringProperties as gtDoubleProperties.
The setting of the monitoring flag is done in the "registerMonitoringProperty" function.
With this kind of changes the developers of other modules have to recompile but not to change their code.
How Has This Been Tested?
Manual. Please check the usage also while the review.
Checklist:
[ ] A test for the new functionality was added (if applicable).
[ ] All tests run without failure.
[ ] The changelog has been extended, if this MR contains important changes from the users's point of view.
[ ] The new code complies with the GTlab's style guide.
[ ] New interface methods / functions are exported via EXPORT. Non-interface functions are NOT exported.
[ ] The number of code quality warnings is not increasing.
The separate class GtMonitoringProperty and the specific classes GtDoubleMonitoring (and int and string) are not necessary if the abstract property has a flag if it is a monitoring one.
Description
The class GtMonitoringProperty is removed.
The GtAbstractProperty now has a flag for monitoring properties.
The existing usages are replaced by "normal" properties. To reduce the need of code changes a "using" is added to read e.g. GtDoubleMonitoringProperties as gtDoubleProperties.
The setting of the monitoring flag is done in the "registerMonitoringProperty" function.
With this kind of changes the developers of other modules have to recompile but not to change their code.
How Has This Been Tested?
Manual. Please check the usage also while the review.
Checklist:
EXPORT. Non-interface functions are NOT exported.