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

Allow closing the Host, Database, and first Query tab #1884

Open
Germs2004 opened this issue Dec 18, 2023 · 2 comments
Open

Allow closing the Host, Database, and first Query tab #1884

Germs2004 opened this issue Dec 18, 2023 · 2 comments

Comments

@Germs2004
Copy link

Is your feature request related to a problem? Please describe.
If I have 5 query tabs open, there's no obvious way to close the first one. Only tabs 2-5 have an X button. Double clicking that first tab doesn't close it - it only clears it, leaving an empty, unwanted Query tab.

Also, must the Host and Database tabs always be visible? You could not load them by default, and only show them if the user right clicks on the Host or Database entry in the tree view and chooses Host Properties or Database Properties. They take up space in the tab list and put more text on the screen for the user's eyes to parse.

Describe the solution you'd like
Add an X button to that first Query tab. If we click the X or double click the tab, close it completely instead of just blanking it.

Do not load the Host or Database tabs by default.

This would leave the tab list fully under the user's control.

Describe alternatives you've considered
Maybe you could continue to leave the first Query tab open and clear it, but only if it's the only Query tab remaining. But, since clicking the "Open a blank query tab" button is so quick and easy, it doesn't seem necessary to leave that one tab open all the time.

Additional context

@ansgarbecker
Copy link
Collaborator

Note the default tabs are intentionally non-closable, intentionally. This is a design decision, meant for new users having a stable look at the application.

@Germs2004
Copy link
Author

Thank you for the reply. I am myself a new user, and found it unexpected and unpreferable, personally. When I see a tab list, my initial impression is that it's for things I am working on and want to switch between, like tabs in a web browser, file explorer, or SSMS. In those cases, there are no forced tabs. I'd guess the host and database properties aren't things people usually need when writing or troubleshooting SQL scripts. My new user perspective is that those things should be available behind a menu click, like the HeidiSQL User Manager, Preferences menu, and many other rarely-needed things.

I fully respect your decision though, and sincerely appreciate this great tool.

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