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

Unsynced wallet status should be more apparent #8060

Closed
laanwj opened this issue May 16, 2016 · 8 comments
Closed

Unsynced wallet status should be more apparent #8060

laanwj opened this issue May 16, 2016 · 8 comments

Comments

@laanwj
Copy link
Member

laanwj commented May 16, 2016

Currently the wallet shows warning triangles on the "Overview" page when the client is not synced.

Looking at the volume of mail I receive from people confused by unsynced client behavior, as well as issues like #7235 this is not enough.

I think it would make sense to:

  • Make the warning look more serious. E.g. make the icons red or yellow instead of the same color as the rest.
  • The warning should appear on every page, not just Overview but also when receiving or sending transactions. Possibly on the bottom bar.
  • Mouseover should warn that:
    • Transactions are not up to date - most notably, received transactions more recent than the current synchronization time are not yet visible. This should be made really, really clear.
    • Balance is not up to date - it does already say this implicitly by showing the triangle next to the balance and recent transactions, but not everyone picks up this hint.
    • Fee estimation is not up to date/incomplete - maybe we need a separate warning for this on the "Send" page.
@jonasschnelli
Copy link
Contributor

Agree with @laanwj. I pick this up.

@Tyler-Hardin
Copy link
Contributor

@laanwj how do you envision this? I'm interested in implementing it, but I don't see a way that's not massively redundant. We already have the sync progress bar and the text warning to the left of it.

What do you think about adding a red or yellow caution to the right of the warning text, to draw attention to it? That seems to best fit with what already exists. Augmenting instead of duplicating. I could change the mouse over text from the sync bar/text to reflect the extra warnings you describe, and add this mouse over to the new warning icon as well.

How does all that sound?

@laanwj
Copy link
Member Author

laanwj commented Jul 18, 2016

@Tyler-Hardin sounds good to me!

@jonasschnelli
Copy link
Contributor

I have a different approach:
If you start, or getting in a state where your Bitcoin-Core GUI is "out-of-sync", we could overlay the MainWindow with an info-layer (maybe slightly semi-transparent) that could inform about the out-of-sync state (warning with some text), the required blocks to catch up, maybe current blocks-per-seconds rate, etc.

Users could "click-away" that modal information layer. But at least a click-away action is required. Once the layer has been clicked away, we could go back to the current state where we show the exclamation mark warning icons

@maflcko
Copy link
Member

maflcko commented Jul 18, 2016

Sound good as well. Make sure to include a "[ ] Never show this again" toggle.

@maflcko
Copy link
Member

maflcko commented Sep 25, 2016

Most of this was done in #8371. Not sure if those should be addressed:

(copied from OP)

  • Transactions are not up to date - most notably, received transactions more recent than the current synchronization time are not yet visible. This should be made really, really clear.
  • Balance is not up to date - it does already say this implicitly by showing the triangle next to the balance and recent transactions, but not everyone picks up this hint.
  • Fee estimation is not up to date/incomplete - maybe we need a separate warning for this on the "Send" page.

@laanwj
Copy link
Member Author

laanwj commented Sep 25, 2016

Hm, doesn't the overlay take care of all of those? I don't mind that they're not specifically implemented as mentioned there, that was just an idea.

@maflcko maflcko closed this as completed Sep 25, 2016
@maflcko
Copy link
Member

maflcko commented Sep 25, 2016

It is missing the fee estimation part, but I think this can be done later.

@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants