Originally Posted by rslotpole
I notice that when you use route manager and put in a date and time it doesn't save that information - is that a known bug?
The departure date and time are indeed not part of the permanent route attributes, but I do not think this is a bug.
Saving this information along with the route would create problems in other areas.
Splitting and joining routes would need answering some questions...
A saved route might become later part of a layer, with the departure date becoming unmodifiable and potentially not meaningful ...
Better to keep the basic route very simple.
One might think of a more permanent object called, say, "route scenario" or "route plan", grouping together all the relevant data per every actual waypoint ETA (effectively what is seen in Route Properties Dialog), but this is not often worth saving, as every time the scenario looks different.
I agree that re-entering the departure time other than ">" may be annoying, so it would be nice to put in the buttons for e.g. "Now", "1 day later" and "3 hours later", as I have done some years ago in a custom 2.5 variant...