Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unresponsive Interface #3764

Closed
cyberduck opened this issue Sep 28, 2009 · 4 comments
Closed

Unresponsive Interface #3764

cyberduck opened this issue Sep 28, 2009 · 4 comments
Assignees
@dkocher
Labels
bug core worksforme

Comments

@cyberduck
Copy link
Collaborator

df02722 created the issue

When I click on the window, I either get a pause before Cyberduck becomes selected, or I get the "waiting" pinwheel.
When I try to drag and drop to upload, I have to wait close to 20 seconds before CD recognizes the drag and drop functionality. Also, if I try to hover over the CD icon in the dock, while dragging items, and I drop the items in, through Expose, the cyberduck window stays in its "preview" position long after the Expose window is gone. It snaps back after a wait.

However, file transfer still work and the progress bar is updated in real time.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

What is your hardware configuration?

@cyberduck
Copy link
Collaborator Author

sardion commented

I've got the same issue.
MacBook (late 2007 model, 2GHz Core 2 Duo, 2GB RAM). Snow Leopard 10.6.1, Cyberduck 3.3b4.

Anytime I use the drag and drop (either to the Finder or from it), there's about 5-10 seconds of spinning wheel both before and after the operation.

I upgraded the system in place from Leopard, and installed the Cyberduck beta on top of the old 3.2 I was using.

Nothing in any log files to indicate whats going on.

If there's any way I can test/help, please let me know. I'll check back on this ticket often.

@cyberduck
Copy link
Collaborator Author

sardion commented

Update: deleting the app and the prefs file and the Application Support/CyberDuck folder and then reinstalling fixed this.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 sardion]:

Update: deleting the app and the prefs file and the Application Support/CyberDuck folder and then reinstalling fixed this.

If you still have the files please send me a copy.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug core worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck