Skip to content

Conversation

@random-zebra
Copy link

@random-zebra random-zebra commented Mar 7, 2020

Fix UnlockContext class 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.

@random-zebra random-zebra added Feature Request GUI Wallet Needs Release Notes Placeholder tag for anything needing mention in the "Notable Changes" section of release notes labels Mar 7, 2020
@random-zebra random-zebra added this to the 4.1.0 milestone Mar 7, 2020
@random-zebra random-zebra self-assigned this Mar 7, 2020
Copy link
Collaborator

@Fuzzbawls Fuzzbawls left a 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

@random-zebra
Copy link
Author

Styling consistency changes have been grouped in the first commit (and expanded to include all files edited).

@random-zebra random-zebra removed the Needs Release Notes Placeholder tag for anything needing mention in the "Notable Changes" section of release notes label Mar 9, 2020
@random-zebra
Copy link
Author

Rebased.

@random-zebra
Copy link
Author

Rebased

@random-zebra
Copy link
Author

Rebased, and added unlock context for "upgrade to HD" flow.
Ready for review / testing.

furszy
furszy previously approved these changes Mar 21, 2020
Copy link

@furszy furszy left a 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 .

@random-zebra
Copy link
Author

Commits squashed as per request.

@furszy
Copy link

furszy commented Mar 23, 2020

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
@random-zebra
Copy link
Author

Rebased... again.

Copy link
Collaborator

@Fuzzbawls Fuzzbawls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK aa7ff86

@random-zebra random-zebra merged commit cc07268 into PIVX-Project:master Mar 23, 2020
random-zebra added a commit that referenced this pull request Mar 23, 2020
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.."):

  ![backup1](https://user-images.githubusercontent.com/18186894/77027832-8d4f8b00-6997-11ea-88b5-d48ec64dc318.png)

  If the user clicks "OK", and the wallet is locked, the unlock dialog is directly shown (as per #1387)

  ![backup2](https://user-images.githubusercontent.com/18186894/77027846-94769900-6997-11ea-8638-b59a11836fb3.png)

  After the upgrade, the client directly presents this dialog:

  ![backup3](https://user-images.githubusercontent.com/18186894/77028494-38ad0f80-6999-11ea-9fe4-1d1f06cf8c7c.png)

  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
JSKitty pushed a commit to ZENZO-Ecosystem/ZENZO-Core that referenced this pull request Apr 16, 2020
Style changes will be left for a later cleanup PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

3 participants