Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signals: path signals for tunnels and bridges #4196

Closed
DorpsGek opened this issue Nov 2, 2010 · 3 comments
Closed

Signals: path signals for tunnels and bridges #4196

DorpsGek opened this issue Nov 2, 2010 · 3 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Nov 2, 2010

palzkillm opened the ticket and wrote:

Hi,

to go along with the other cheat functions or maybe as a general enhancement, I would suggest to add path signals for tunnels and bridges. This would allow for larger constructions to be used more efficiently.

From an interface perspective, the best way to handle this would surely be to be able and use the normal signal interface on tunnels and bridges.
An easier way to solve this could be to add a context menu to tunnels and bridges where the path signal could be set or unset, but only for the entire construction.

Marco

Reported version: 1.0.4
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/4196
@DorpsGek
Copy link
Member Author

DorpsGek commented Sep 3, 2011

private_paula wrote:

HackaLittleBit allready has a patch including this feature.
Maybe the devs can have a look at it for easy and fast implementation ;)

http://www.tt-forums.net/viewtopic.php?f=33&t=41260&start=0# p754200


This comment was imported from FlySpray: https://bugs.openttd.org/task/4196#comment10304

@DorpsGek
Copy link
Member Author

andythenorth wrote:

Flyspray clean up: possibly a long term goal for OpenTTD, but difficult to implement cleanly. Not a current goal for OpenTTD, so reducing priority.

Eddi has looked at the HackaLittleBit patch and believes that it's not a viable solution, and would create a development dead end for other related features.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4196#comment14559

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
@andythenorth
Copy link
Contributor

andythenorth commented Apr 13, 2018

Classic big pony. It's known that the feature is wanted, but it has serious implementation challenges, and nobody wants to push it through.

So let's pass on this one :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

2 participants