-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Quick way to swap between depature and arrival time #548
Comments
For me, that looks good. If all the features of the second toolbar is available from the menu, showing it could be optional. BTW talking about novice users: Shouldn't the menu (now with the ^v icon) be accessible via a "hamburger" icon? |
There's no more menu.
hamburger icons are for navigations drawers. In this screen, there's none. |
Ah, I see. I thought the ^v icon is for a menu ... |
Related to #600 |
It took me some time to even find that there is an option to set the time to arrival time. So i also think a switch in the time pickerwould be best. |
This is now realized in Transportr 2.1.0, see #664 . |
Acknowledgments
Please check the following boxes with an
x
if they apply:Is your feature request related to a problem? Please describe.
More often than not, I am using Transportr to find the time, when I have to leave to be at my destination at a certain time. It is frustrating, that I have to click the clock icon to set the time and then the Menu icon > Time is > Arrival.
I also believe, this uses more data, because as soon as I set the time, Transportr checks for connections at the new time.
Describe the solution you'd like
IMHO the best way would be, to have a toggle in the screen for entering the time. This toggle would switch between departure and arrival time. The reason why I believe, this is the best place, is as follows: Nearly all of the time when searching for connections to be at the destination at a certain time, the time setting screen has to be called up.
Describe alternatives you've considered
A discussion about this can be found at #383
The text was updated successfully, but these errors were encountered: