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
In the main program, the public properties in Encoder classes exposes distance values as centimeters, while the other sensors utilizes meters.
This may cause confustion for the people writing control logics for the vehicle.
Two alternative options that would fix the issue:
Option 1:
Add aditional metod reporting distance in meters (in addition to cm).
This would mean an increment of the minor version (new functionality but no breaking change).
Option 2
Change methods in main program to utilize values as meters instead of centimeters.
Modify the Encoder page and overview page to also reflect these changes (the displayed units).
This would mean an increment of the major version (breaking change for code allready using data from the encoders).
PS:
The microcontroller should still transfere the distance as centimeters and a whole number.
The change should only be carried out in the main program (dividing the received distance by 100).
In the main program, the public properties in Encoder classes exposes distance values as centimeters, while the other sensors utilizes meters.
This may cause confustion for the people writing control logics for the vehicle.
Two alternative options that would fix the issue:
Option 1:
This would mean an increment of the minor version (new functionality but no breaking change).
Option 2
This would mean an increment of the major version (breaking change for code allready using data from the encoders).
PS:
The microcontroller should still transfere the distance as centimeters and a whole number.
The change should only be carried out in the main program (dividing the received distance by 100).
PPS:
The versioning refered to above in the two options is based on Semantic Versioning 2.0.0
The text was updated successfully, but these errors were encountered: