Iain,
Stop 1 is the start location. Kind of like the Windows Start menu is used to stop Windows.
If I get ambitious I might decide to replace Stop verbiage with Start verbiage when there are no ¡°Stops¡±.
The graph size is based on the window size. It expands or contracts to fill the graph window.
Dave Sand
toggle quoted message
Show quoted text
On Dec 12, 2018, at 12:26 PM, Iain <iain@...> wrote:
I am reading the Timetable introduction prior to trying it out. I am on version 4.12 and I will probably hold off doing anything until 4.14 is issued since I don't really want to do 2 upgrades.
I am happy that I understand things in general, but I get a bit lost with how Trains are "introduced" and "removed". For example a Train has Stops (at Stations) - so far so good. But a Train must start from a Stop, mabye even half way through a Segment. But there seems to be no description of how you identify which Stop it starts at.
As an example - look at BT and GT on the Timetable Graph. They both start at Epsilon and ultimately come back there having waited for some time at Beta and Gamma respectively. All good stuff and exactly what I would expect/want. But nowhere on the Train or Stop paragraphs does it say how I tell the system that a train initially starts or finally stops at a particular Station/Stop.
I am lucky that UK trains have a Train Reporting Number (TRN) which is 4 characters, but the compression on the graph may make things undistinguishable. Can the user expand the graph or break it into pages (presumably this might be done by using several Schedules covering (say) 4 hours at a time? What about the trains which are on a boundary though when a Schedule stops?
If I want to introduce trains into the system I am presuming I could have a separate Segment representing my notional Carriage Sidings from which trains could be collected and returned.
