opening a new tab should use current tab's connection not the connection of the last executed query

Craig shared this idea 3 years ago
Under Consideration

A new tab's connection is based on the connection of the last executed mongo command. Seems to me to make more sense if the new tab's connection is based on the currently active tab's connection. The user's brain is solving a problem in the current tab, so if they request a new tab it is very likely that she is thinking in that context rather than the connection from potentially many tabs in the past.

An even simpler example: with multiple tabs open each with a different connection, execute a query in a tab #1. Then close tab #1. You return to tab #2 and continue working on the code but without executing any queries. Then open a new tab -- it will use the connection of closed tab #1. That strikes me as unintuitive, even surprising.

Replies (1)

photo
1

By default, the new tab will use the connection of the connect tree's focus node. If you want to use current tab's connection, click "CTRL+SHIFT+T" or double-click the header of tab to clone/duplicate the current tab.

photo
1

Ah, ok. Great description. Where that breaks down, however, is in the situation I outlined above when you close the tab that has the tree with the focus. When I open the tab it's using the focus of a closed tab? That seems counter-intuitive to me, no?

photo
1

This is indeed a problem. I will consider adding a feature that allows switching/creating connection within the script tab.

Shown below

/Aw8Y8p2ZReJrAAAAAElFTkSuQmCC

photo
Leave a Comment
 
Attach a file