Ende einer Zugfahrt/en: Unterschied zwischen den Versionen
Aus RailRoad&Co.-Wiki
Zur Navigation springenZur Suche springen
Uslex (Diskussion | Beiträge) Die Seite wurde neu angelegt: „* Ending a train journey does not remove it from memory.“ |
Uslex (Diskussion | Beiträge) Die Seite wurde neu angelegt: „Operations initiated during the ongoing train journey can still contain references to the still existing train journey, even if they are only executed after the train journey has ended.“ |
||
| Zeile 22: | Zeile 22: | ||
* Ending a train journey does not remove it from memory. | * Ending a train journey does not remove it from memory. | ||
Operations initiated during the ongoing train journey can still contain references to the still existing train journey, even if they are only executed after the train journey has ended. | |||
<div lang="de" dir="ltr" class="mw-content-ltr"> | <div lang="de" dir="ltr" class="mw-content-ltr"> | ||
Version vom 21. Dezember 2025, 10:09 Uhr
| Verwendung |
|
Train journey in the attic
How long does a train journey remain in memory?
How long does a train journey remain in memory after it has ended?
I would like to use a macro that queries the current train journey after a delay to output a message.
Ending a train journey does not remove it from memory
Mr. Freiwald describes it in the forum:
A train journey remains in memory until it is removed from memory by the user using the Delete command.
- Ending a train journey does not remove it from memory.
Operations initiated during the ongoing train journey can still contain references to the still existing train journey, even if they are only executed after the train journey has ended.
- Das ist nicht aus Versehen so.
- Sondern es wurde im Gegenteil einiges investiert, damit dies so ist.
Wäre es anders, könnten sehr viele nach Beendigung einer Zugfahrt sinnvollen Dinge nicht mehr umgesetzt werden.
Weblinks
- Quelle: Forum
- -- Uslex (Diskussion) 09:51, 21. Dez. 2025 (UTC)
