diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2017-07-25 14:10:32 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2017-07-25 14:10:57 +0200 |
| commit | 412b466d11ffc8c68a65104b6c14bde15c0a9b4d (patch) | |
| tree | 4f6ccc0f2ad9d4d06cf1c8320c4ef01089ebc499 /contrib/linearize | |
| parent | 1124328ad1e8b1d4487d81404eff269c5373d6a7 (diff) | |
| parent | 97375727b8f3b7d26c7c813630a6139005b5c5c9 (diff) | |
Merge #10870: [Qt] Use wallet 0 in rpc console if running with multiple wallets
9737572 [Qt] Use wallet 0 in rpc console if running with multiple wallets (Jonas Schnelli)
Pull request description:
Current master with multiwallet results in accessing wallet 0 in QT (send / receive / tx history / etc.), **but** the RPC console cannot access that wallet (only non-wallet commands work).
This is a quick solution to re-allow accessing the same wallet (Index 0) via RPC console in multiwallet.
The solutions design is not "state of the art" (should go over WalletModel). Ideally we work on an overall multiwallet support for the GUI (which then would remove this change).
I think we should consider this as a bugfix.
Tree-SHA512: 16cf844662248ffd3d82c7d0cbe5879f231fbc7d4f5a4aab4180a9087018519c98301e4ac311eaec2cc39dddf25d3edf9be99a6622ea682c138a820a9b21fd0c
Diffstat (limited to 'contrib/linearize')
0 files changed, 0 insertions, 0 deletions