-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Minor - P4
-
Affects Version/s: 1.20.5
-
Component/s: Connectivity
-
None
-
Environment:OS: Debian, installed via .deb package
-
Iteration Cantaloupe
Every time I use the "connect to" feature to select where to connect, Compass appears to reload itself.
To reproduce:
1. Open Compass (wait for loading UI)
2. In menu go to connect -> connect to
3. Wait for loading UI again
As a user of Compass, once it is loaded I expect it to stay loaded and not reload itself for as long as the program is running.
—
I think I understand what is happening: using "connect to" duplicates the application. While I imagine this is a useful feature, I would also like to be able to replace the active connection/application instance with a connection to another deployment without reloading the application, especially given that connection attempts cannot be aborted (https://jira.mongodb.org/browse/COMPASS-4237).
- related to
-
COMPASS-4237 "New connection" process cannot be interrupted
- Closed