Racetime condition caused different data display on startup, as sometimes the transactions were displayed before the data to check if it is a channel event for example was available. Now when everything is available the outdated entries will get updated.
Refreshing the list did not redraw the elements, therefore it was not possible to fix those outdated entries without scrolling them out of the view and then scrolling back.
Now refreshing the view by pulling down does what it should. It refreshes.
Switching the currency while on the list caused some cached entries not to update leading to mixed currency display.
Node or contact names were often not displayed as the data was available after the list was created.
Simplified code
Motivation and Context
The inconsistent display of data in the transaction history is very confusing for users.
So this PR should improve the UX a lot
Most likely fix #267
How Has This Been Tested?
My S9 on mainnet
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
Here is what is fixed / changed now:
Motivation and Context
The inconsistent display of data in the transaction history is very confusing for users. So this PR should improve the UX a lot Most likely fix #267
How Has This Been Tested?
My S9 on mainnet
Types of changes
Checklist: