[roeter]

A series of blueprints has been issued, in particular for proposals for timetable and signalling functions.
To keep some line in the discussion I will open a series of threads on the various subjects.

This is the first and it's a very simple and basic function :
blueprint for print position

It's just a little help for route-builders.

Regards,
Rob Roeterdink

[James Ross]

roeter, on 07 March 2017 - 01:16 AM, said:

This is the first and it's a very simple and basic function :
blueprint for print position

It's just a little help for route-builders.

The idea is good, but I'd prefer we log this to the standard log file for now, and don't provide any options for it, but it can include multiple lines in the log, including marker-file format.

Additional logging settings are not going to help things when we already have the "Data logger" and "Evaluation", both of which need reworking IMHO, at which point we can integrate these log items into the reworked solution.

[roeter]

One drawback with having the info in the log file is that it will get rather 'lost' among all the other information.
A more serious drawback is that the logfile is superseded if you start a new session. So you must always edit the logfile and take the data out to another file to saveguard the info.
The advantage of a separate file (which at present is always appended, not replaced) is that the information is available until you explicitly delete it. If you don't get round to dealing immediately with whatever it was, the information will still be there. Not so with the logfile.

Regards,
Rob Roeterdink

[James Ross]

roeter, on 20 March 2017 - 02:09 PM, said:

One drawback with having the info in the log file is that it will get rather 'lost' among all the other information.
A more serious drawback is that the logfile is superseded if you start a new session. So you must always edit the logfile and take the data out to another file to saveguard the info.
The advantage of a separate file (which at present is always appended, not replaced) is that the information is available until you explicitly delete it. If you don't get round to dealing immediately with whatever it was, the information will still be there. Not so with the logfile.

That's all true...

I don't feel like the options for what format to log, etc., are that worthwhile in the grand scheme of settings-clutter (which is already fairly bad) so if we could at least start off with no settings that would make me happier.

And since we have a (hidden) setting called "LoggingPath" (which defaults to your desktop and is where the log file is put), could we start by putting a new file there, with the data is multiple formats like I suggested for the log file? Maybe OpenRailsMarkers.txt or something similar.

If people do really show an interest and, say, want a CSV-format output of this or another specific format we can look at a drop-down choice for it.

[roeter]

James Ross, on 20 March 2017 - 03:23 PM, said:

And since we have a (hidden) setting called "LoggingPath" (which defaults to your desktop and is where the log file is put), could we start by putting a new file there, with the data is multiple formats like I suggested for the log file? Maybe OpenRailsMarkers.txt or something similar.

Sounds fine, I will use that.

Regards,
Rob Roeterdink