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
Unable to set custom keyboard shortcuts #7720
Comments
I cannot reproduce this issue. Make sure you also assign a new shortcut for Info (⌘-I) and New Browser (⌘-N) to replace the default shortcuts. |
At times I could get it to show up in the menu bar but the keyboard shortcut key would not actually work. I think you may have got the keyboard shortcuts to show up in the menu bar but were you actually able to use them to open the info window, and to toggle the creation of a new site? Another one I had trouble with was "disconnect" which I attempted to assign to |
Ok - just tested again and seems like if I do make sure the existing shortcut has been replaced, then I can assign the new one. But I also have to restart the Cyberduck app to make the changes take effect. I would just like to note that both of these things are different from the default way all other apps ( that I've seen so far ) manage keyboard shortcuts. In other apps:
So, it works, but it seems like Cybderduck handles keyboard shortcuts in a non-standard way which was leading me to think it was broken. Thanks for checking into it. |
Replying to [comment:5 cwd]:
I am not aware we have any custom handling of keyboard shortcuts but rely on the system frameworks. |
I've tried to use the Preferences dialog in OS X to set custom keyboard shortcuts for CyberDuck - a few of them being:
"New Bookmark" works but "Disconnect" and "Edit Bookmark" are not working very well. In the menu the old keyboard shot disappeared but the new keyboard shotcut does not show up - and the assigned keyboard shortcut ( for example, Disconnect ) just does what it previously did - Duplicate.
Attachments
keyboard-prefs.png
(117.6 KiB)screen.png
(29.1 KiB)The text was updated successfully, but these errors were encountered: