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

Make it more clear which is the selected session, e.g. for firing queries #785

Open
albertotn opened this issue Oct 30, 2019 · 4 comments
Labels

Comments

@albertotn
Copy link

@albertotn albertotn commented Oct 30, 2019

Steps to reproduce this issue

  1. Step 1; start program
  2. Step 2; connect to a server ( localhost or remote )

Current behavior

Current query host/connection information is not prominent

immagine

Expected behavior

User interface could possible highlight current query target ( localhost / aws in my example).
Imagine query tabs with query on multiple connections, could be potentially very confusing to understand where a query is executed.

Possible solution

In query tab before query name (query 1). display also connection name, so it's easy to spot where a query is executed.

Environment

  • HeidiSQL version:

Last version, 10.2.0.5730

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

@ansgarbecker ansgarbecker commented Oct 30, 2019

In query tab before query name (query 1). display also connection name, so it's easy to spot where a query is executed.

Having the session name in each query tab would make the user think these tabs are bound to that session, which is not true. As soon as you navigate to another session, any query fired in any tab runs on that selected session.

What if the tree on the left would gray out unselected sessions even more than they are now?

Other ideas?

@albertotn

This comment has been minimized.

Copy link
Author

@albertotn albertotn commented Oct 30, 2019

Having the session name in each query tab would make the user think these tabs are bound to that session, which is not true. As soon as you navigate to another session, any query fired in any tab runs on that selected session.

Totally missed that, my bad. I must be more cautious on this, good to know!

What if the tree on the left would gray out unselected sessions even more than they are now?
Other ideas?

Add an option for users to activate a "only one connection at time", so it's more hard to mess things up

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

@ansgarbecker ansgarbecker commented Oct 31, 2019

I should probably also make the selected database and its root node bold:

grafik

ansgarbecker added a commit that referenced this issue Nov 1, 2019
…e object, so we get bold focused path there as well. Related to #785
@ansgarbecker ansgarbecker changed the title Current server host in window title bar Make it more clear which is the selected session, e.g. for firing queries Nov 1, 2019
@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

@ansgarbecker ansgarbecker commented Nov 1, 2019

Next build has bold text for any node in the focused database tree path.

Your idea also sounds not bad, to limit the number of simultaneous connections to 1, optionally. I just wonder if that will be used by more than a very few users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.