Genma Saotome, on 10 February 2017 - 06:15 PM, said:
Just for the record, I want to repeat a suggestion I've been offering for some time. Sprite text -- ALL sprite text -- should be displayed only if it is marked for display in the specific activity which is running. IMO that would greatly reduce the amount of text that is displayed at any given moment in time and by definition restrict the text to uniquely serve the information needs of each activity.
Please check X3991's new "auto" mode for station and siding labels which I have just added. It will show any station platform or siding label that the train is due to stop at or is mentioned in the work order, in both activity and timetable modes. You can still cycle through the existing three options (all labels, all platforms, and all sidings).
Genma Saotome, on 10 February 2017 - 06:15 PM, said:
It needn't be anything more complex than making a copy of the routes .tit file, deleting everything in it that isn't a platform or siding (with text) that is desired for an activity, and saving it as <ActivityFileName>.tit. THAT identifies which sprite text to display in that activity, assuming the OR team changes the code to make use of it. No more unwanted sprites (of any intensity).
We'll consider adding an activity-specific list of which items to label, but let me know how X3991's "auto" mode does.
mbm_OR, on 05 June 2017 - 05:15 AM, said:
When we use the TrainsList window or the Dispatcher window to switch from Player-Train to another Ai-train, if the new active train does not stop at the station, we do not have any reference to know where it is, no labels with 'F6 activity' selected.
I'm afraid I don't follow what you're saying here.
mbm_OR, on 05 June 2017 - 05:15 AM, said:
Activity mode stores all stations that use specific traffic in ...TCRoute.StationXRef, and after adding some code, we can know if it is a platform or a siding and its name. With it, we can see all the platforms or sidings labels, by where the traffic has to make its path.
But in TimeTable mode, we can't use ...TCRoute.StationXRef, the easier way. I do not know if it exists with different reference in TimeTable mode.
The only way I found was to use ...StartList.StationStops, but it only let us know the station stops, for the current train, ignoring the rest of the stations where the train does not stop.
That might be the case, but I've gone and used Train.StationStops which works in both activity and timetable mode. :)
mbm_OR, on 05 June 2017 - 05:15 AM, said:
It is easy to debug code in Activity mode, but it's difficult to do it in TimeTable mode.
Every time I needed to know which code stored some kind of data, the only way was to dump it into a text file, a very tedious job.
Maybe there is an easier way to debug the TimeTable mode code, but I have not yet found it.
I am not sure what's harder to debug in timetable mode; both modes can be run under the debugger just fine (as I have just done).