Order the address book by date #57
Comments
cmihai
added a commit
to cmihai/unit-e
that referenced
this issue
May 3, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
cmihai
added a commit
to cmihai/unit-e
that referenced
this issue
May 3, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
cmihai
added a commit
to cmihai/unit-e
that referenced
this issue
May 7, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
cmihai
added a commit
to cmihai/unit-e
that referenced
this issue
May 7, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
cmihai
added a commit
to cmihai/unit-e
that referenced
this issue
May 7, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
cmihai
added a commit
to cmihai/unit-e
that referenced
this issue
May 7, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
cmihai
added a commit
to dtr-org/unit-e
that referenced
this issue
May 8, 2019
This commit extends the `CAddressBookData` structure with a new field, `timestamp`, representing the creation or modification time of the address. It also adds a new argument to the `filteraddresses` RPC call, which allows sorting by the timestamp field, either in ascending or descending order. Required for implementing dtr-org/unit-e-desktop#57. Signed-off-by: Mihai Ciumeica <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Right now, the address book is returned (by calling the
filteraddressesRPC) either unsorted, or sorted by label. When the user generates a new address, this address is therefore not the first in the list of displayed addresses on the "Receive" page, so the user has to scroll through the entire address book to find it and copy it (e.g. to receive a payment).Expected behavior
When the user presses the
New addressbutton, the newly generated address replaces the previous one on the page, so the user can immediately copy it to clipboard or scan the associated QR code.The text was updated successfully, but these errors were encountered: