Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The standard RSS update with XmlListModel/ListView does not work by some reason.
After some time, the ListView gets out of sync with the XMLListModel and it shows
wrong content (already deleted emails, nothing at all etc.). It maybe caused by
some incorrect "id" field in the RSS entries? I don't know, but if the "id" as key
removed from the model, the all items are always updated in the RSS fetch causing
"new email arrived" messages always
The current workaround contains two XmlListModels, one to calculate the correct
amount of new emails with "id" as key and a second without "id" associated with the
ListView. Since the second updates all items always, it is unlikely that the ListView
goes out-of-sync.
I know this is not a correct fix just a workaround, but I could not come up anything better without extensive debugging since the original implementation is simple and it should not have any problem.