At the right side we see the open connection among each other. It is difficult to see which connection you are working with. If each connection is on its own tab, you can switch between the connections more easily, and it remains clear which connection you are working on.
Put every connection on a Tab
Ok, that's the approach HeidiSQL is using now since several years. A tab interface involves a lot changes to the whole UI.
and it remains clear which connection you are working on
There are more aspects in that idea than this.
The current UI is intentionally one tree, so users still are able to see all connections at least with a part of their databases. That's a benefit when you're working on similar systems, like a dev server and live server.
For a better separation between different connections, I had introduced session background colors (like that light blue in the attached screenshot). Also, the focused connection nodes are painted in normal text color, while the other ones are dimmed to a grey.
If you collapse the database tree. You see couple of lines per connection.
But if you expand the table tree and it is bigger than I can see, and I have 3 open connections I have to search in which connection I work.
When I execute a SQL statement I have to check Iam in the right database. Especcialy in a test and live database/connection.
But it can be a option for the end user. Than they can choose the best option for them.
Several years ago (must have been up to v3.1, see https://sourceforge.net/p/heidisql/tickets/365/ ), HeidiSQL had a multi-document-interface (MDI), which was horrible. Users complained about having to resize controls for each connection. There was then my idea to support multiple connections in one tree, which helped a lot. Just being a bit nostalgic...
Please login to leave a reply, or register at first.