You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v.7.12 Cyberduck did not always open a new window for a new connection (from bookmarks). Cyberduck re-use an existing window and switch the connection. Example: one window with server A, one with Server B. If I open another connection for Server C, Cyberduck re-use one of the windows for Server A or B to connect Server C.
This wasn't before the latest update.
The text was updated successfully, but these errors were encountered:
I cannot reproduce that a new window would be opened when double clicking a bookmark to connect. Do you refer to the restore of windows when re-opening the application?
I cannot reproduce that a new window would be opened when double clicking a bookmark to connect. Do you refer to the restore of windows when re-opening the application?
no.
If Cyberduck already running and one connection-window is open, I choose new a connection from the bookmark menu.
Sometimes it will open a new window, sometimes CD will switch the connection of the existing window.
Same will happen if I select "show bookmarks" and choose another connection from there. Also sometimes "show bookmarks" will shown in on existing connection-window instead of open a new window.
A very annoying behavior!
" This should always open the connection in the current open browser window."? Why? This is not a feature, this is a bug and wasn't like this before in previous versions of Cyber Duck. If you working with several different server, you need for each one a own connection window! At least it should be configurable in the settings.
Since v.7.12 Cyberduck did not always open a new window for a new connection (from bookmarks). Cyberduck re-use an existing window and switch the connection. Example: one window with server A, one with Server B. If I open another connection for Server C, Cyberduck re-use one of the windows for Server A or B to connect Server C.
This wasn't before the latest update.
The text was updated successfully, but these errors were encountered: