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
I recently updated Cyberduck, and when it restarted after the installation, I got a message that said this (see attachment):
"Cyberduck has been updated. Do you want to allow the new version to access the same keychain items (such as passwords) as the previous version?"
Then my choices were a "Don't Change" button, and a "Change All" button.
My beef is that the question in the Cyberduck update message is a Yes or No question, but my choices have nothing to do with "Yes" or "No". Likewise, the message does not mention the word "change" at all, so that just adds to the confusion.
My recommendation would be that if you ask a Yes or No question, provide buttons that say "Yes" and "No". You can't get much more clear than that.
Thanks for your detailed report. The dialog is provided by Apple and I cannot change it. However, Cyberduck is now code signed which should make this dialog disappear after you have trusted it once.
OK, so this isn't a bug, but it is an irritant.
I recently updated Cyberduck, and when it restarted after the installation, I got a message that said this (see attachment):
"Cyberduck has been updated. Do you want to allow the new version to access the same keychain items (such as passwords) as the previous version?"
Then my choices were a "Don't Change" button, and a "Change All" button.
My beef is that the question in the Cyberduck update message is a Yes or No question, but my choices have nothing to do with "Yes" or "No". Likewise, the message does not mention the word "change" at all, so that just adds to the confusion.
My recommendation would be that if you ask a Yes or No question, provide buttons that say "Yes" and "No". You can't get much more clear than that.
Thanks for listening.
Mark Neukom
Attachments
CyberDuck Irritant.jpg
(49.6 KiB)The text was updated successfully, but these errors were encountered: