Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review screen does not use custom speed units #14

Open
leezer3 opened this issue Jan 1, 2016 · 2 comments
Open

Review screen does not use custom speed units #14

leezer3 opened this issue Jan 1, 2016 · 2 comments

Comments

@leezer3
Copy link
Owner

leezer3 commented Jan 1, 2016

Custom speed units can now be set via Route.DisplaySpeed but these are not reflected in the review screen.

Requires changing.

@leezer3
Copy link
Owner Author

leezer3 commented Jan 1, 2016

Note:
Section & signal speed limits are displayed in the F10 debug window in km/h
These possibly ought to be changed, although I'm in two minds about this, as speeds in the routefile are in km/h, and this screen isn't really for driving use,

@mgavioli
Copy link
Contributor

mgavioli commented Mar 8, 2016

Another case are overspeed messages, which also are always in km/h, regardless of the route setting.

I understand your concern about the F10 debug window; still, I imagine it can be useful to route developers to have that indication in the route specific speed unit. What about having both km/h and mph (one reported from route data and the other computed), at least for mph routes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants