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
When planing a Trip in the future it makes sense to show multiple options before and after the selected time of arrival, so the user can pick the best one. However it makes no sense to show options from the past that are impossible to take. None at all or maybe a maximum of 5min ago, in case the user wants to run I guess. The current situation is not optimal though. The whole screen is filled with trips that can't be taken as seen in the screenshot. It just doesn't make sense to fill up the ui with useless information like that.
To Reproduce
Steps to reproduce the behavior:
Select a location and destination
Select a time of arrival today, that's still possible to arrive at, but not too far off in the future
Transportr shows trips from the past
Expected behavior
Transportr doesn't show trips that are impossible to take
Screenshots
Versions (please complete the following information):
Transportr Version: 2.2.1
Device: Pixel 4a 5G
Android Version: 14 (GrapheneOS)
The text was updated successfully, but these errors were encountered:
Describe the bug
When planing a Trip in the future it makes sense to show multiple options before and after the selected time of arrival, so the user can pick the best one. However it makes no sense to show options from the past that are impossible to take. None at all or maybe a maximum of 5min ago, in case the user wants to run I guess. The current situation is not optimal though. The whole screen is filled with trips that can't be taken as seen in the screenshot. It just doesn't make sense to fill up the ui with useless information like that.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Transportr doesn't show trips that are impossible to take
Screenshots
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: