You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Wallet model class uses a Dictionary keyed by Account (numbers) to store account properties. When used as an IEnumerable, the order is not defined. This can cause the ObservableCollection of recent accounts in the shell view model (which does have an ordering) to order the accounts in an implementation dependent manner.
I think the best way to solve this issue is to maintain a sorted List of accounts and their properties in the Wallet class. Other than the imported account (which is planned to be removed from btcwallet in a later update), all accounts numbers are strictly increasing.
The text was updated successfully, but these errors were encountered:
jrick
added a commit
to jrick/Paymetheus
that referenced
this issue
Apr 12, 2016
The Wallet model class uses a Dictionary keyed by Account (numbers) to store account properties. When used as an IEnumerable, the order is not defined. This can cause the ObservableCollection of recent accounts in the shell view model (which does have an ordering) to order the accounts in an implementation dependent manner.
I think the best way to solve this issue is to maintain a sorted List of accounts and their properties in the Wallet class. Other than the imported account (which is planned to be removed from btcwallet in a later update), all accounts numbers are strictly increasing.
The text was updated successfully, but these errors were encountered: