Point to note: You couldn't turn trams around until some time after I complained.
The guys who coded trams didn't want to add it. With any new feature in OpenTTD, there's always this resistance against making it fit the game. I can understand the feeling, but I'm fed up with it!
If it had been up to me, it would've been a parameter. Just like 90 degree curves, I think they are completely unrealistic as you would never see any tram doing that IRL, but are still useful for a few gameplay purposes.
In real life if things go completely pear shaped you could drive the tram in the opposite direction on the same physical track and/or use a crossover onto the track heading in the opposite direction, which isn't an option in OpenTTD.
Some types of in-game road vehicle jam/deadlock are almost impossible to recover without turning vehicles around.
Separately, the bug with station names being clickable despite being hidden...
... Was a bug in master that's now fixed.
That has also been merged into my branch, so it'll be in the next release.
(like, letting them turn around)
I wonder how hard that would be to code. No sarcasm intended here. Is it really possible to code a button for planes to turn around, but only on ground ?
Having aircraft able to turn around at arbitrary points is likely to make it more difficult to design a fully correct and sensible movement state machine.
Road vehicles are allowed to take over each other IRL just as in OpenTTD because we consider you have great visibility and speed (unless you're taking over a snail).
In game overtaking doesn't work for articulated vehicles, which is a slight snag.
It's also rather too conservative in the case of one-way roads, which is a whole extra can of worms.
I would like to remind suggestion about possibility of cloning/using template consist of expired vehicles, in case of "use remain vehicles" button is active.
I have been thinking about this and the UI implications are not really that straightforward.
The use vehicles in depot and keep remainders toggles can only be used after the template has been created.
Normal users are likely to be confused if they create and apply a template which can't actually be constructed, and are not made aware of that fact.
I don't really want to add yet another setting.
So allowing creation of the template, but clearly warning and/or requiring user confirmation would seem plausible.
Confirmation dialogs are a bit problematic and introduce unpleasant lifetime/raciness issues at clone time.
A prominent warning message on the template would then seem the most practical.