-
Notifications
You must be signed in to change notification settings - Fork 725
[GUI] Add Unlock/Relock context flow #1387
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
[GUI] Add Unlock/Relock context flow #1387
Conversation
33d651e to
39e5562
Compare
Fuzzbawls
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concept ACK, with the same concern as in #1389 with style-only changes being in their own commit
39e5562 to
153088d
Compare
|
Styling consistency changes have been grouped in the first commit (and expanded to include all files edited). |
8bbc2dc to
c7eb49a
Compare
|
Rebased. |
c7eb49a to
3f12546
Compare
|
Rebased |
3f12546 to
a195f30
Compare
|
Rebased, and added unlock context for "upgrade to HD" flow. |
a195f30 to
112b541
Compare
furszy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor thing, would be better if we squash 3dcf0ee4 and ae620312 inside the UnlockContext commit as those are changes over code that was introduced there.
Side from that, ACK 112b541 .
112b541 to
498da1d
Compare
|
Commits squashed as per request. |
|
Needs rebase (we should merge this to not continue rebasing it anymore, it's ready to go for me). |
askpassphrasedialog is used instead
Connect the signal emitted by WalletModel::requestUnlock to the TopBar, in order to present the unlock-wallet dialog, before creating the UnlockContext. The wallet will then restore its previous state (Unlocked or UnlockedForStaking) upon destruction of the UnlockContext object.
PWidget::verifyWalletUnlocked replaced with the UnlockContext. Add flows: - Create New Receive Address - Create New Payment Request - Create Masternode Controller - Create Cold Staking Address - Send Cold Stake Delegation - Add multisend recipient
498da1d to
aa7ff86
Compare
|
Rebased... again. |
Fuzzbawls
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK aa7ff86
53cfbee [GUI] Automatic wallet backup after upgrade to HD (random-zebra) Pull request description: Based on - [x] #1387 Offer the option to directly backup the wallet after upgrade-to-HD (and successive re-lock) is completed. The message on the initial dialog is changed (from "Note that you will need to MAKE A NEW BACKUP.."):  If the user clicks "OK", and the wallet is locked, the unlock dialog is directly shown (as per #1387)  After the upgrade, the client directly presents this dialog:  If the user clicks "OK", then the open-file dialog is presented, so the user can select the filename for the backup file and click "Save" completing the flow. If the user clicks "CANCEL" (or dismisses the open-file dialog later), a snackbar popup warns the user, telling to remember to backup asap. ACKs for top commit: furszy: Tested ACK 53cfbee. Fuzzbawls: ACK 53cfbee Tree-SHA512: 80fbcdb4d9805d75db98a0f394840f734314e6d249539997f1948cd7775ac2a81239b762386b7770c6ca4b8a2c38acdf1d5ae7ee7f07591bfdfc7dd4ee39cfc2
Style changes will be left for a later cleanup PR
Fix
UnlockContextclass and connect it where needed.Now, once an action requires the wallet to be fully unlocked, the askpassphrase dialog is presented to the user (if the status is "Locked" or "UnlockedForStaking"). This way, the password can be entered directly, and the operation can resume without needing additional clicks by the user.
The previous locking status is restored when the action completes.
Interested flows:
Also
Closes #553
Closes #1035
And maybe #1152 becomes not needed now.