Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

Default behavior when running behind #9

Open
ghost opened this issue Feb 27, 2015 · 0 comments
Open

Default behavior when running behind #9

ghost opened this issue Feb 27, 2015 · 0 comments

Comments

@ghost
Copy link

ghost commented Feb 27, 2015

  • I'm trying to restrain myself with requests for enhancements since this is a very early version
  • I expect the GUI to behave the same as the client

Having said that, this is something that I may forget later, so I'll put it here:
screenhunter_03 feb 27 17 14

A workaround at present is Preferences > OK. If things are up to date, that will have the GUI show wallet contents.

While client can't do much else than either hang forever or show a similar message and retry or exit thereupon, a GUI could show useful info.

Please consider these possible enhancements:

  • Display a refresh button or icon (which would be the equivalent of clicking on Preferences > OK)
  • Show some stats (current Bitcoin block height/date, current Counterparty server block height/date, current time/date) to give an idea how things are going because otherwise there's no way to know how much longer one needs to wait.
  • (Possibly) show simple wallet details. Although those may not be up to date, they can be useful. For example, if I haven't transacted since last time I used the GUI, those are most likely correct and if I just want to see what's the current balance, I don't need to wait 30 minutes to see my balance (unless I suspect I was robbed). While the same is possible by going to several (one query for for each wallet address) blockchain explorers, this would be much friendlier.
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

1 participant