Skip to content
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][Nit] Cold Staking Address list doesn't repopulate #1296

Closed
CaveSpectre11 opened this issue Jan 22, 2020 · 0 comments · Fixed by #1297
Closed

[GUI][Nit] Cold Staking Address list doesn't repopulate #1296

CaveSpectre11 opened this issue Jan 22, 2020 · 0 comments · Fixed by #1297
Assignees
Milestone

Comments

@CaveSpectre11
Copy link

Describe the issue

When you click away from the staker page, and back to it, when the Cold Staking Addresses list is being displayed, it does not redraw.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

  1. From the "Staker" pane. click on "My Cold Staking Addresses" to show the list of addresses. Note the arrow goes from pointing right to pointing down.
  2. Click to the "Delegation" pane.
  3. Click back to the "Staker" pane.
  4. Notice the Cold Staking Addresses arrow still points down, but no staking addresses are listed.
  5. Click on the "My Cold Staking Addresses". See the arrow doesn't change position, and the list populates.

Expected behavior

Either reset the arrow to the right on page display, or repopulate the list on page display; but don't draw the arrow in the down position without the list displayed.

Actual behavior

The arrow is pointed down (like it's displaying a list) but the list isn't there. Clicking will generate the list.

Screenshots.

If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
image

What version of PIVX Core are you using?

Pivx v4.0.2

Machine specs:

  • OS: Linux (Ubuntu 18.04) and Windows 7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants