-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] XF5.0.0-pre5 ItemsSource/CollectionView regressions #13548
Comments
I can't stress how time consuming these two regressions are, and would really appreciate if they were resolved. 5.0.0 stable and later versions are a nightmare to work with until these get resolved. |
@jsuarezruiz Any chance this could also get a blocker label? CollectionViews no longer updating at all when their data is batch updated is a real blocker, even more so with the performance regression when updating them one item at a time. These are regressions, and pretty fatal at that, so if they could go to the top of a service release and a fix be put out ASAP would be much appreciated! Thank you. |
There have been a ton of issues in 5.0.0 regarding ItemsSource modifications. I really think that hard-coding ItemsSource contents in an XAML file while testing is not enough as it doesn't replicate a real-world scenario. ItemsSources are often asynchronously populated (for example residing in a view model, where the vm itself downloads the data). Hard-coding ItemsSource contents in an XAML file masks any such issues and does not correlate with real-world usage, resulting in an unnecessary number of regressions. |
Hello @hartez. Pinging again regarding these regressions -- do you have an estimate on when they will be fixed? I'm hoping for a service release or a point release soon, as you can't currently fill up a CollectionView with data properly. Thanks so much. |
@jsuarezruiz @hartez I'd really appreciate some correspondence on these four CollectionView bugs I have opened: I spent a ton of time isolating the issues and making repro projects for them, and I need some kind of resolution as I have a hard time finish up my work here before they are resolved. So I'd really appreciate some comments on time estimates, or any kind of correspondence regarding them. |
@Tommigun1980 Thanks for the repro sample: #13126 (comment) |
Thank you so much @jsuarezruiz! These two issues in this report are so tough as they make CollectionViews almost impossible to populate. Any chance of adding a regression and high prio flair to this? The last working version was XF5.0.0-pre4. The workaround is permeating my entire code-base at this point. |
This issue is a compilation of other issues. I mark this issue as verified, since the issues it points to are verified but duplicated (to close when there is a fix and the others are closed). @Tommigun1980 Yes, added high label to #13231. |
any eta on these getting fixed?.. these were updated february last? |
Description
Opening a new ticket to get some traction on this.
XF5.0.0-pre5 introduced the following regressions that probably go hand in hand, where updating a CollectionView's ItemsSource no longer works:
Both cases worked in XF5.0.0-pre4 and versions prior to it.
So there is no way to properly populate collection data in XF5.0.0-pre5 or later.
More detailed breakdown:
Repro project at #13126 (comment). Presumed duplicates or very closely related to this issue: #13530, #13361. Another repro project at #13231 (bugs 1 and 2).
Original report at #13429.
This on iOS - I don't know if it happens on Android also.
Steps to Reproduce
Repro project for 1) at #13126 (comment), repro case for 2) would be the same project but remove the
BeginMassUpdate()
line (to prevent batching).Expected Behavior
XF5.0.0-pre5 and later should update the UI when batch updating ObservableCollection contents.
XF5.0.0-pre5 and later should not slow down to a crawl when updating ObservableCollection contents one by one.
Actual Behavior
Basic Information
Environment
Show/Hide Visual Studio info
Workaround
To force refresh a CollectionView after batch updating its ItemsSource collection, do the following:
The text was updated successfully, but these errors were encountered: