When using a massive wallet with many tx's, when SD starts up, it's quite slow and it takes a long time to render all the data. In my transactions tab, just after starting SD, I can switch to it and see some transactions, of addresses that have the fewest tx's and return their RPC data the quickest. But it's a partial or incomplete transaction list and it can be very confusing for a user that is looking to verify a tx happened. The data will "magically appear" seconds or minutes later, and the user is never told they were looking at incomplete data or that all tx data has not been returned.
A simple message or spinner in the transaction tab would solve this: Show a message and/or spin a spinner until all RPCs for all addresses have returned tx data, on initial load. After initial load, we can decide to use the same thing, or not.
When using a massive wallet with many tx's, when SD starts up, it's quite slow and it takes a long time to render all the data. In my transactions tab, just after starting SD, I can switch to it and see some transactions, of addresses that have the fewest tx's and return their RPC data the quickest. But it's a partial or incomplete transaction list and it can be very confusing for a user that is looking to verify a tx happened. The data will "magically appear" seconds or minutes later, and the user is never told they were looking at incomplete data or that all tx data has not been returned.
A simple message or spinner in the transaction tab would solve this: Show a message and/or spin a spinner until all RPCs for all addresses have returned tx data, on initial load. After initial load, we can decide to use the same thing, or not.
When using a massive wallet with many tx's, when SD starts up, it's quite slow and it takes a long time to render all the data. In my transactions tab, just after starting SD, I can switch to it and see some transactions, of addresses that have the fewest tx's and return their RPC data the quickest. But it's a partial or incomplete transaction list and it can be very confusing for a user that is looking to verify a tx happened. The data will "magically appear" seconds or minutes later, and the user is never told they were looking at incomplete data or that all tx data has not been returned.
A simple message or spinner in the transaction tab would solve this: Show a message and/or spin a spinner until all RPCs for all addresses have returned tx data, on initial load. After initial load, we can decide to use the same thing, or not.