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
Is your feature request related to a problem? Please describe.
There is currently no simple way to view the travel time between class/lecture locations in the timetable view, making it hard to plan consecutive slots such that the travel time is feasible.
Describe the solution you'd like
As in the image, I would like to add a "bubble" to each lesson slot, that shows travel distance and estimated travel time, which its color corresponds to whether it would be possible to make it in time for that lesson. As well as a button to toggle the visibility of these "bubbles".
Describe alternatives you've considered
Could potentially expand into a daily route planner as well?
The text was updated successfully, but these errors were encountered:
Upon working on the implementation, I'm realising that it may provide more functionality if the travel time is displayed as a custom timetable cell as in the image.
Such that when the "travel cell" is clicked we may add a menu for the user to see the venues of the consecutive lessons on a map, and potentially to open the 2 venues in google maps for directions.
Is your feature request related to a problem? Please describe.
There is currently no simple way to view the travel time between class/lecture locations in the timetable view, making it hard to plan consecutive slots such that the travel time is feasible.
Describe the solution you'd like
As in the image, I would like to add a "bubble" to each lesson slot, that shows travel distance and estimated travel time, which its color corresponds to whether it would be possible to make it in time for that lesson. As well as a button to toggle the visibility of these "bubbles".
Describe alternatives you've considered
Could potentially expand into a daily route planner as well?
The text was updated successfully, but these errors were encountered: