[Klonan] [2.0.23] Trains: Renaming Surface-Unique Stop affects multi-surface Interrupt

[fakusb]

1. What did you do?
   On Nauvis, I have a train network with many stops of the same name (`Load 1-2-1 Cargo). On Fulgora, I have exactly one stop of the same name. The train stop is used inside train schedule interrupts of a train group that has several trains, both on Nauvis and Fulgora. I renamed the single train station on Fulgora (without holding ctrl).
2. What happened?
   The train stop on Fulgora was renamed. Also the name inside the interrupt of the train group was renamed (Both as "target" and in the condition, "check not full station"). The train stops on Nauvis were not renamed. This means that trains on Nauvis now have a broken schedul (as the names in their schedule are different from the names of the stops on nauvis).
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
   I would have expected only the one train stop on Fulgora are renamed, but the names in the Interrupt are unchanged.
   In other words: A train stop in an interrupt is only renamed if it was either globally unique, or crtl was holded while renaming.[/size]
4. Does it happen always, once, or sometimes?
   Always.

Some more experimentation seems to shop that the same "broken schedules for nauvis" problem also occurs if there are more than one stop of the name on Fulgora, and ctrl is used while renaming. It seems that renaming train stops does not combine with sharing train schedule interrupts on different surfaces.

Maybe related: viewtopic.php?f=11&t=106370&hilit=rename+train+stop

[Klonan]

Thanks for the report

This is now fixed for the next release

The name in interrupts will only be replaced if the train stop is the last using that name across all surfaces.