UI: show complete path to wallet.dat on Wallet-Repair tab#641
Merged
eduffield222 merged 4 commits intodashpay:v0.12.1.xfrom Oct 26, 2015
Merged
UI: show complete path to wallet.dat on Wallet-Repair tab#641eduffield222 merged 4 commits intodashpay:v0.12.1.xfrom
eduffield222 merged 4 commits intodashpay:v0.12.1.xfrom
Conversation
crowning-
changed the title
|
👍 |
|
Thanks :) |
eduffield222
pushed a commit
that referenced
this pull request
Oct 26, 2015
UI: show complete path to wallet.dat on Wallet-Repair tab
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reference: https://dashtalk.org/threads/can-the-dash-wallet-show-actual-dat-file-names.6469/
I think this is a quite useful idea. I placed it on the Wallet-Repair tab because that's the place you need to know which wallet you're actually repairing,
Tested on all 3 platforms without problems.
Looks like this:
Sorry for the commit-fest, but there seems to be some differences between Qt4 and Qt5 on Windows platforms.