[Weter]

I see 2 benefits at this way:
Today You are user, tomorrow-developer and vice-versa.
If paragraphs are clearly marked "for deveopers", then new user can spare many time and effort, not reading hard-to understand information (248 pages in English is hard for me, for instance), but he can access, compare and summarise information of interesting topic from the same *.pdf, if he need.

From the other hand, separate Advanced User Guide can spare many pages for them, who knows MSTS, or ORTS basics already.

[cjakeman]

I've been corresponding with ErickC and am now able to make a change to suit his Item 1.

ebnertra000, on 17 July 2020 - 11:48 AM, said:

New OR-specific signal script functions. I know Rob wrote up a document on it, but I don't know how much of it has made its way into the manual as of yet

This is the next one on our thread.

 signalling_operational.pdf (82.81K)
Number of downloads: 941
Is this the document that you were thinking of (from 2013) or was it something more recent?

[roeter]

This is the latest version. It so happens that only last week I found that a specific approach_control function was missing. I have now included this function.
To avoid confusion, I have also added the date to the filename. Most of this has not found its way into the manual, mainly because the tooling used to generate the manual somehow will not work on my laptop, so I would be working 'blind' and that's not a proper way to write a manual.

 SignalFunctions_20200729.pdf (143.25K)
Number of downloads: 777

Regards,
Rob Roeterdink

[charland]

How about basic instructions on how to set up a proper installation of folders. Maybe where to get the proper contents of the SOUND and GLOBAL folders.

Paul

[cjakeman]

roeter, on 29 July 2020 - 10:42 AM, said:

This is the latest version. It so happens that only last week I found that a specific approach_control function was missing. I have now included this function.
To avoid confusion, I have also added the date to the filename.

That's great.

Thanks, Rob.

[cjakeman]

charland, on 29 July 2020 - 11:15 AM, said:

How about basic instructions on how to set up a proper installation of folders. Maybe where to get the proper contents of the SOUND and GLOBAL folders.

Can you help to provide these, Paul?

[cjakeman]

roeter, on 29 July 2020 - 10:42 AM, said:

Most of this has not found its way into the manual, mainly because the tooling used to generate the manual somehow will not work on my laptop, so I would be working 'blind' and that's not a proper way to write a manual.

I've had problems too installing the MiKTeX element of the tooling. Eventually I copied it from a PC where it was already working so I can produce the entire manual as a PDF.

I've also discovered that, if I use the free Visual Studio Code IDE to edit the *.rst files, then I can install an extension that gives me a preview so with a single keystroke, I can go from this:




to this:



It's generating HTML rather than a PDF.
I had to fiddle quite a bit so I've saved some notes, in case anyone else wants to try it.

[cr-stagg]

charland, on 29 July 2020 - 11:15 AM, said:

How about basic instructions on how to set up a proper installation of folders. Maybe where to get the proper contents of the SOUND and GLOBAL folders.

Paul

What is wrong with section 4.4? It is very basic. And section 4.5.1 for what and where from for the files needed. Again it is just basic. For all contingencies to be covered it would be far from basic.

[Weter]

Quote

Control mode shows the actual control mode. Read more about this here.

7.18. Analysis Tools page 69
Link to paragraph about control mode is missing.

[cjakeman]

Hi Weter,

Weter, on 02 August 2020 - 03:57 AM, said:

7.18. Analysis Tools page 69
Link to paragraph about control mode is missing.

Thanks for this. Any more corrections will be gratefully received and acted on.

ebnertra000, on 17 July 2020 - 11:48 AM, said:

New OR-specific signal script functions. I know Rob wrote up a document on it, but I don't know how much of it has made its way into the manual as of yet

This work is also under way.

[eugenR]

Hi
Rob Röterdink has published here a pdf for TimetableChanges at the end in the first post:
http://www.elvastowe...ode-signalling/
Perhaps somebody can also entered this Informations in the Manual in the Chapter 11 ?

Regards
EugenR

[cjakeman]

eugenR, on 08 August 2020 - 08:09 AM, said:

Rob Röterdink has published here a pdf for TimetableChanges at the end in the first post:
http://www.elvastowe...ode-signalling/
Perhaps somebody can also entered this Informations in the Manual in the Chapter 11 ?

Thanks for linking back to that document, Eugen.

To copy Rob's text from a PDF into the manual involves using the RST markup, which is designed to be quick and simple. Then the document is submitted to GitHub. I would be happy to help with the technology.

Is anyone willing to take this task on?

[roeter]

cjakeman, on 09 August 2020 - 12:30 AM, said:

Thanks for linking back to that document, Eugen.

To copy Rob's text from a PDF into the manual involves using the RST markup, which is designed to be quick and simple. Then the document is submitted to GitHub. I would be happy to help with the technology.

Is anyone willing to take this task on?

Latest version for timetable commands is here.
There is a MS-word version available if that helps. If anyone is interested, just let me know.

Regards,
Rob Roeterdink

[rickloader]

Hi Chris, Rob, I would like to try and help with timetables and the manual.
Rick

[Weter]

Waiting for new functional's descriptions, I've found it very difficult to read 243 pages over and over, in order to search new text.
Why not to place timestamps, showing each paragraph's update time?
Then each one can see clearly, where's the new information, and where's no, so not to re-read old paragraphs again.