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
{{ message }}
This repository has been archived by the owner on Feb 14, 2022. It is now read-only.
It's the issue with conversion from Number to Float and in reverse. I should track down where this issue lies
And, also a solution: we need to return from the app server endpoint the speed number, but in String format. So, it will be displayed as a String, ommitting issues such as displaying "0.20000" instead of just "0.2", and for speed dial this string will be converted to float, and then we will get our result: dial data will be more accurate, and we will have a speed number like "7.4" before 10 km/h (or for you fellow Americans mph)
The text was updated successfully, but these errors were encountered:
It's the issue with conversion from Number to Float and in reverse. I should track down where this issue lies
And, also a solution: we need to return from the app server endpoint the speed number, but in String format. So, it will be displayed as a String, ommitting issues such as displaying "0.20000" instead of just "0.2", and for speed dial this string will be converted to float, and then we will get our result: dial data will be more accurate, and we will have a speed number like "7.4" before 10 km/h (or for you fellow Americans mph)
The text was updated successfully, but these errors were encountered: