Feature: Hide block signal tools by default #7504
Conversation
| default: | ||
| break; | ||
| } | ||
| } |
There was a problem hiding this comment.
Isn't there a better way to hide widgets? Planes or something?
There was a problem hiding this comment.
The only planes I've had success finding anything about in OTTD are airplanes, but there may be some corner of NUI that I still haven't discovered exists.
There was a problem hiding this comment.
Yeah an attempt at wrapping the buttons with an NWID_SELECTION on each row caused massive problems, it's much more trouble than worth to do it "the right way". May as well re-do the entire signals UI then.
| @@ -1556,6 +1556,8 @@ STR_CONFIG_SETTING_SEMAPHORE_BUILD_BEFORE_DATE :Automatically b | |||
| STR_CONFIG_SETTING_SEMAPHORE_BUILD_BEFORE_DATE_HELPTEXT :Set the year when electric signals will be used for tracks. Before this year, non-electric signals will be used (which have the exact same function, but different looks) | |||
| STR_CONFIG_SETTING_ENABLE_SIGNAL_GUI :Enable the signal GUI: {STRING2} | |||
| STR_CONFIG_SETTING_ENABLE_SIGNAL_GUI_HELPTEXT :Display a window for choosing signal types to build, instead of only window-less signal-type rotation with Ctrl+clicking on built signals | |||
| STR_CONFIG_SETTING_SHOW_BLOCKSIGNALS :Enable building block signals: {STRING2} | |||
| STR_CONFIG_SETTING_SHOW_BLOCKSIGNALS_HELPTEXT :Show the tools for building block signals and pre-signals. Usage of block signals and path signals is discouraged, since path signals usually solve the same problems better. Existing block signals will continue working. | |||
There was a problem hiding this comment.
Not a fan of this, reads as very disparaging to the user. Something like "Block & pre(not path!) signals are intended for advanced users only"
| @@ -1556,6 +1556,8 @@ STR_CONFIG_SETTING_SEMAPHORE_BUILD_BEFORE_DATE :Automatically b | |||
| STR_CONFIG_SETTING_SEMAPHORE_BUILD_BEFORE_DATE_HELPTEXT :Set the year when electric signals will be used for tracks. Before this year, non-electric signals will be used (which have the exact same function, but different looks) | |||
| STR_CONFIG_SETTING_ENABLE_SIGNAL_GUI :Enable the signal GUI: {STRING2} | |||
| STR_CONFIG_SETTING_ENABLE_SIGNAL_GUI_HELPTEXT :Display a window for choosing signal types to build, instead of only window-less signal-type rotation with Ctrl+clicking on built signals | |||
| STR_CONFIG_SETTING_SHOW_BLOCKSIGNALS :Enable building block signals: {STRING2} | |||
There was a problem hiding this comment.
Maybe "Enable block signal GUI", as per "Enable the signal GUI" above. Or perhaps it should just be rolled into the same setting and be made a tri-state
|
Honestly this is a poor solution to the wrong problem, I'll rather remake the signals UI entirely. |
Please stop building block signals and especially pre-signals. They're for the most part a bad idea and your networks will function much better with PBS. Let's hide it behind an Expert level setting.