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

Feature Request: Hide TC button when not needed? #8

Open
Lord-Naul opened this issue Nov 4, 2018 · 3 comments
Open

Feature Request: Hide TC button when not needed? #8

Lord-Naul opened this issue Nov 4, 2018 · 3 comments

Comments

@Lord-Naul
Copy link

If there's no Blizzy's toolbar, everything defaults to Stock App Toolbar, in which case, do we need to display the TC app button?

YMMV but once I've got my toolbars setup, I don't need to change them very often.

I'd like to propose:

  1. let users set 'none' for the TC button (It seems when TC loads (and registers itself?) it flags noneAllowed = False so even editing the config file manually blocks us)
  2. Add a button in the Game Difficulty settings window to launch the TC main window (or add it back to a toolbar)
    image
  3. Default config if there is only one toolbar manager (stock), useStock = False
@linuxgurugamer
Copy link
Owner

That was a deliberate decision. TC allows you to fully hide buttons as well as decide which toolbar to put them on. As such, I am loathe to make it removable, from experience I know that I will get people asking for help because it was missing.
I'll talk to some people, see what they think

@Lord-Naul
Copy link
Author

What if on KSP launch when TC is loading it defaults to on, but could be turned off (until next time KSP is relaunched)? I could see that being an issue for folks with large mod collections taking a while to relaunch KSP though, which is why I suggested adding a button to the advanced game options window.

@linuxgurugamer
Copy link
Owner

Start a discussion in the ToolbarController thread, let's get other chiming in. No offense, but a change like this really needs more input. It's not difficult, but it's the way it's working right now, and would be a pretty significant change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants