mirror of
https://github.com/keepassxreboot/keepassxc.git
synced 2025-05-10 02:25:38 -04:00
Add ellipsis
The rule for ellipsis is simple: If the described action requires interruption (typically by a dialog) which requires user input, then ellipsis should be used to indicate that triggering the menu will not immediately trigger the desired action. Examples: "Save" does not need an ellipsis in general (when the file name is known) "Open..." needs an ellipsis, as one must select a file to open. "Save as..." needs an ellipsis, as in order to save the file as something, one must select a file name. "About" does not need an ellipsis, while it may open a dialog, that dialog is the desired result.
This commit is contained in:
parent
c0f668c4bb
commit
f71d0c0da8
2 changed files with 9 additions and 9 deletions
|
@ -73,7 +73,7 @@ Database* KeePass2Reader::readDatabase(QIODevice* device, const CompositeKey& ke
|
|||
quint32 signature2 = Endian::readUInt32(m_headerStream, KeePass2::BYTEORDER, &ok);
|
||||
if (ok && signature2 == KeePass1::SIGNATURE_2) {
|
||||
raiseError(tr("The selected file is an old KeePass 1 database (.kdb).\n\n"
|
||||
"You can import it by clicking on Database > 'Import KeePass 1 database'.\n"
|
||||
"You can import it by clicking on Database > 'Import KeePass 1 database...'.\n"
|
||||
"This is a one-way migration. You won't be able to open the imported "
|
||||
"database with the old KeePassX 0.4 version."));
|
||||
return nullptr;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue