[COMPASS-4234] Application reloading every time I "connect to" Created: 10/Apr/20 Updated: 27/Oct/23 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Connectivity |
| Affects Version/s: | 1.20.5 |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Oleg Pudeyev (Inactive) | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: Debian, installed via .deb package |
||
| Issue Links: |
|
||||||||
| Sprint: | Iteration Cantaloupe | ||||||||
| Description |
|
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) 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). |
| Comments |
| Comment by Massimiliano Marcon [ 22/Apr/20 ] |
|
Yes, you are correct: connect to opens a new window to connect to a new server/cluster. |