aboutsummaryrefslogtreecommitdiff
path: root/src/qt/askpassphrasedialog.cpp
diff options
context:
space:
mode:
authorMichael Dietz <michaeldietz@Michaels-MacBook-Air.local>2020-11-27 14:18:50 -0600
committerMichael Dietz <michaeldietz@Michaels-MacBook-Air.local>2020-11-27 14:18:50 -0600
commit8008ef770f3d0b14d03e22371314500373732143 (patch)
treede7654e339764599173be1322866dd6d7c89bc5a /src/qt/askpassphrasedialog.cpp
parente2ff5e7b35d71195278d2a2ed9485f141de33d7a (diff)
downloadbitcoin-8008ef770f3d0b14d03e22371314500373732143.tar.xz
qt: unlock wallet "OK" button bugfix
When trying to send a transaction from an encrypted wallet, the ask passphrase dialog would not allow the user to click the "OK" button and proceed. Therefore it was impossible to send a transaction through the gui. It was not enabling the "OK" button after the passphrase was entered by the user, because it was using the same form validation logic as the "Change passphrase" flow.
Diffstat (limited to 'src/qt/askpassphrasedialog.cpp')
-rw-r--r--src/qt/askpassphrasedialog.cpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/qt/askpassphrasedialog.cpp b/src/qt/askpassphrasedialog.cpp
index 3b4967421a..3be8b664dd 100644
--- a/src/qt/askpassphrasedialog.cpp
+++ b/src/qt/askpassphrasedialog.cpp
@@ -199,6 +199,8 @@ void AskPassphraseDialog::textChanged()
acceptable = !ui->passEdit2->text().isEmpty() && !ui->passEdit3->text().isEmpty();
break;
case Unlock: // Old passphrase x1
+ acceptable = !ui->passEdit1->text().isEmpty();
+ break;
case ChangePass: // Old passphrase x1, new passphrase x2
acceptable = !ui->passEdit1->text().isEmpty() && !ui->passEdit2->text().isEmpty() && !ui->passEdit3->text().isEmpty();
break;