I know that the idea behind EITs is to reduce overheads associated with triggers used for scheduling. However, I have one case where I either need to make extensive changes in schedules for all trains transiting through a small yard by adding intermediate trackmarks and ITPath commands, or use a trigger or trackmark prior to the yard to schedule an ITPath for the transiting trains. I cannot use an automatic path and path trigger because it conflicts with the few trains that DO use that yard.
Question for Pierre: "ScheduleAtTrackmark" rule in versions before TANE (kuid2:61392:2001:4) had the option to Insert (not Append) a command string BEFORE the current command in the trains schedule and the current schedule command was retained after the inserted command. This option went away in kuid2:61392:2001:6, and only "replace current command" and "append" to schedule are options now. I did use it with my old TRS2010 route to dynamically amend a schedule, Is there a reason this can no longer be done? If I have this option, I can use it like before to solve this problem.
Question for Pierre: "ScheduleAtTrackmark" rule in versions before TANE (kuid2:61392:2001:4) had the option to Insert (not Append) a command string BEFORE the current command in the trains schedule and the current schedule command was retained after the inserted command. This option went away in kuid2:61392:2001:6, and only "replace current command" and "append" to schedule are options now. I did use it with my old TRS2010 route to dynamically amend a schedule, Is there a reason this can no longer be done? If I have this option, I can use it like before to solve this problem.