What is the accepted / best method for sorting / filtering an ObervableCollection in Community Toolkit MVVM?

[GamingCity]

Hi,
im wanted to ask about this because i ran out of ideas at this point
A have a ObservableCollection with about 300 UserControls that need sorting and filtering based on their DataContext properties.
And is displayed in a ItemsControl.

Right now im using the method of sorting / filtering in a list and then use that to toggle visibility and move items in the observable collection. While this works, it is slow and it is starting to become difficult to add more options and maintain.

I tried with this, but it dosent work. Probably because im not using ReactiveUI. Im using Community MVVM with compiled bindings.
https://docs.avaloniaui.net/docs/concepts/reactiveui/binding-to-sorted-filtered-list

[stevemonaco]

DynamicData is technically separate from ReactiveUI (though it's used by and maintained by their team, in part). You can import the System.Reactive and DynamicData packages into an Mvvm Toolkit app.

However, ReactiveUI has some nice extensions that you may need. I'm not sure how easily these can be included in your app without also taking a dependency on ReactiveUI. Even if you do, you can use Mvvm Toolkit + ReactiveUI side-by-side if you're careful about it. This is what I've done in the past, but the extra dependency didn't really matter.

An alternative is ObservableCollections + R3 which should also be usable with Mvvm Toolkit. It's a much newer framework so I haven't really tested it yet. They have an Avalonia sample at https://github.com/Cysharp/ObservableCollections/blob/6f5de33bff1cad05b3ad4ff56583ad4919ba9f9c/sandbox/AvaloniaApp/MainWindow.axaml.cs

[stevemonaco]

Also, your ObservableCollection shouldn't contain UserControls. These should be ViewModels.

[GamingCity]

Yes, sorry, i meant viewmodels for the user controls.

[GamingCity]

Ok, i took a look at ObservableCollections and i went for that, it was nearly a drop-in replacement of the stock one and the only thing i needed is to have a different hook for the UI. That allows to implement an easy Sort() function by just implementing the corresponding interface on the items.

On top of that R3 is what gaves you filters, that work if the data on the items changes, but there is no way to tell it that the data that the filter is comparing to has changed whiout re-attaching the filter what is not fast. What is no good for implementing, a search by string, specially if you do it without a search button.
So i decided not to use R3 and instead implementing my own filtering that toggles the visibility of items, what is really fast for the amount of items im filtering.

Thanks for pointing me to it.