Skip to content

Conversation

@furszy
Copy link

@furszy furszy commented Mar 13, 2020

This was built on top of #1399.

Essentially connecting the HD wallet upgrade to the GUI as it was defined in the release-notes in #1327.

@furszy furszy self-assigned this Mar 13, 2020
@Fuzzbawls
Copy link
Collaborator

needs rebase now that #1399 has been merged

@furszy furszy force-pushed the 2020_gui_upgrade_wallet branch from a457dbd to aa6e3d1 Compare March 14, 2020 14:35
@furszy furszy force-pushed the 2020_gui_upgrade_wallet branch from aa6e3d1 to 42ed283 Compare March 14, 2020 14:50
@furszy
Copy link
Author

furszy commented Mar 14, 2020

Done, PR rebased.

@random-zebra random-zebra added this to the 4.1.0 milestone Mar 15, 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.

styling changes mostly, but some observations:

  1. from the release notes: "A dialog will appear on every wallet startup notifying you that you are running a pre-HD wallet and letting you upgrade it from there." doesn't look like any such dialog notice is implemented just yet, but I do see the expandable button allowing HD upgrade.

  2. when using the UI to upgrade to HD wallet, maybe we should provide a UI dialog notice confirming the upgrade was successful?

  3. Post-upgrade, the HD expandable button remains until wallet restart

@furszy
Copy link
Author

furszy commented Mar 16, 2020

PR updated.

Answering the observations:

  1. yep, just included it.
  2. There is a notification coded already, just fixed the issue. The method was not being called properly.
  3. Same issue as 2, fixed.

And added the jump lines to the method brackets.

Copy link

@random-zebra random-zebra left a comment

Choose a reason for hiding this comment

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

This looks good to me.
Only two considerations:

  • 10 seconds of delay before showing the update dialog after startup seems "weird" to me (it basically shows up when you already started to perform some operation, e.g. sending or whatever). I would make it just 2 or 3 seconds max.

  • Clicking accept on the upgrade dialog (with locked wallet) presents another dialog which says to unlock and how to proceed afterwards.
    This would be nicer if the unlock dialog were presented instead, and the user could directly insert his password (instead of clicking close --> unlocking --> clicking the HD button to upgrade).
    This can be achieved rebasing this PR on top of #1387.
    Or alternatively we can merge this one, and add this flow to #1387 later.

@furszy
Copy link
Author

furszy commented Mar 17, 2020

The idea behind the 10 seconds delay was to have the wallet running properly before the notification gets launched (sometimes the first window show is not so smooth -- varies over the different OS and machine resources --). But sure, we can decrease it to possibly 4 seconds.

And about the unlock context point, agree. Would merge this and create a new PR once #1387 gets merged.

@furszy furszy force-pushed the 2020_gui_upgrade_wallet branch from 90a0b29 to 0e969f1 Compare March 17, 2020 15:27
Copy link

@random-zebra random-zebra left a comment

Choose a reason for hiding this comment

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

ACK 0e969f1

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 0e969f1

@random-zebra random-zebra merged commit d8663a8 into PIVX-Project:master Mar 18, 2020
@furszy furszy deleted the 2020_gui_upgrade_wallet branch November 29, 2022 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants