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

timetable editor: does not take in account pattern travel time #216

Open
skinkie opened this issue Jul 12, 2018 · 8 comments
Open

timetable editor: does not take in account pattern travel time #216

skinkie opened this issue Jul 12, 2018 · 8 comments

Comments

@skinkie
Copy link

skinkie commented Jul 12, 2018

image

I would expect that in the timetable editor I only would need to provide the departure time. But the Travel Time is not automatically added:

image

@landonreed
Copy link
Member

I believe you must have created the trip when the pattern had one stop, then added Vlissingen, revisited the timetable editor, and found the stop blank.

Currently this is the expected behavior, but we do recognize that the ideal behavior would be to apply the travel times to existing trips.

@skinkie
Copy link
Author

skinkie commented Jul 12, 2018

No, the pattern was already created. I'll invite you to the project, so you can see for yourself :)

@landonreed
Copy link
Member

Do you mean the pattern already had two stops before creating the trop 0612? I don't think this is the case. If you add a new trip, you should see the travel/dwell time for the stop automatically applied here.

@skinkie
Copy link
Author

skinkie commented Jul 12, 2018

This is what happens if you add a trip to the end:

image

Editing that:
image

So there are quite a view advancements that could be taken here. It should obviously automatically fill in the travel time. But also adding the trip might be done more intuitively. For example by providing the interval time ahead of time in a box next to the "add" button. Additionally it would be a nice feature if you could increase/descrease the time without typing.

@landonreed
Copy link
Member

See #172.

@skinkie
Copy link
Author

skinkie commented Jul 12, 2018

I would like to see that one work. But I hope after typing 21:00:00 it would just update (untouched) fields.

@landonreed
Copy link
Member

Currently, the way to offset all times for a trip is to use the "offset" feature.

@skinkie
Copy link
Author

skinkie commented Jul 12, 2018

I understand, I think the "excel" way of just entering a bunch of times, and the other columns follow, is far more practical.

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