+- 0Day Forums (https://zeroday.vip)
+-- Forum: Coding (https://zeroday.vip/Forum-Coding)
+--- Forum: C# (https://zeroday.vip/Forum-C)
+--- Thread: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread (/Thread-This-type-of-CollectionView-does-not-support-changes-to-its-SourceCollection-from-a-thread-different-from-the-Dispatcher)
This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread - bronsoncixrxnk - 07-24-2023
I have a DataGrid which is populating data from ViewModel by asynchronous method.My DataGrid is :
<DataGrid ItemsSource="{Binding MatchObsCollection}" x:Name="dataGridParent"
Style="{StaticResource EfesDataGridStyle}"
HorizontalGridLinesBrush="#DADADA" VerticalGridLinesBrush="#DADADA" Cursor="Hand" AutoGenerateColumns="False"
RowDetailsVisibilityMode="Visible" >
I am using
[To see links please register here]
to implement asynchronous way in my viewmodel.Here is my viewmodel code:
public class MainWindowViewModel:WorkspaceViewModel,INotifyCollectionChanged
{
MatchBLL matchBLL = new MatchBLL();
EfesBetServiceReference.EfesBetClient proxy = new EfesBetClient();
public ICommand DoSomethingCommand { get; set; }
public MainWindowViewModel()
{
DoSomethingCommand = new AsyncDelegateCommand(
() => Load(), null, null,
(ex) => Debug.WriteLine(ex.Message));
_matchObsCollection = new ObservableCollection<EfesBet.DataContract.GetMatchDetailsDC>();
}
List<EfesBet.DataContract.GetMatchDetailsDC> matchList;
ObservableCollection<EfesBet.DataContract.GetMatchDetailsDC> _matchObsCollection;
public ObservableCollection<EfesBet.DataContract.GetMatchDetailsDC> MatchObsCollection
{
get { return _matchObsCollection; }
set
{
_matchObsCollection = value;
OnPropertyChanged("MatchObsCollection");
}
}
//
public void Load()
{
matchList = new List<GetMatchDetailsDC>();
matchList = proxy.GetMatch().ToList();
foreach (EfesBet.DataContract.GetMatchDetailsDC match in matchList)
{
_matchObsCollection.Add(match);
}
}
As you can see in my Load() method in my ViewModel first I am getting matchList (which is a list of a DataContract Class) from my Service.Then by foreach loop I am inserting my matchList items to my _matchObsCollection(which is an ObservableCollection of DataContract Class)).Now here I am getting the above error (as I shown in Title) "This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread"
![enter image description here][1]
[1]:
Can anyone suggest me any solution.Moreover if possible I would like to know how to bind my DataGrid in View and also refresh it asynchronously if any better way is there.
RE: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread - Prounpartizan778 - 07-24-2023
If I'm not mistaken, in WPF 4.5, you should be able to do this without any problem.
Now to solve this, you should use the synchronization context. Before you launch the thread, you have to store the synchronization context in the ui thread.
var uiContext = SynchronizationContext.Current;
Then you use it in your thread:
uiContext.Send(x => _matchObsCollection.Add(match), null);
Take a look at this tuto
[
[To see links please register here]
][1][1]:
[To see links please register here]
RE: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread - causation378 - 07-24-2023
Since your ObservableCollection is created on UI thread, you can only modify it from UI thread and not from other threads. This is termed as [thread affinity][1].
If you ever need to update objects created on UI thread from different thread, simply `put the delegate on UI Dispatcher` and that will do work for you delegating it to UI thread. This will work -
public void Load()
{
matchList = new List<GetMatchDetailsDC>();
matchList = proxy.GetMatch().ToList();
foreach (EfesBet.DataContract.GetMatchDetailsDC match in matchList)
{
App.Current.Dispatcher.Invoke((Action)delegate // <--- HERE
{
_matchObsCollection.Add(match);
});
}
}
[1]:
[To see links please register here]
RE: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread - kittieglctxow - 07-24-2023
I have experienced the same issue once and resolved the issue with AsyncObservableCollection (
[To see links please register here]
).RE: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread - jenileerz - 07-24-2023
In my case (I populate `ObservableCollection` with asynchronous tasks and do not have access to `App` instance) I use `TaskScheduler.FromCurrentSynchronizationContext()` to cleanup the collection on faulted:
// some main task
Task loadFileTask = Task.Factory.StartNew(...);
Task cleanupTask = loadFileTask.ContinueWith(
(antecedent) => { CleanupFileList(); },
/* do not cancel this task */
CancellationToken.None,
/* run only if faulted main task */
TaskContinuationOptions.OnlyOnFaulted,
/* use main SynchronizationContext */
TaskScheduler.FromCurrentSynchronizationContext());
RE: This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread - Mrsibyllesmtwpwbom - 07-24-2023
If you are using BackgroundWorker you should **raise the event** in the same thread of the UI.
For i.e. if you have two views A and B and the following code inside A raises the event WakeUpEvent
//Code inside codebehind or viewmodel of A
var worker = new BackgroundWorker();
worker.DoWork += WorkerDoWork; //<-- Don't raise the event WakeUpEvent inside this method
worker.RunWorkerCompleted += workerRunWorkerCompleted; // <-- Raise the event WakeUpEvent inside this method instead
worker.RunWorkerAsync();
//Code inside codebehind or viewmodel of view B
public ViewB () {
WakeUpEvent += UpdateUICallBack;
}
private void UpdateUICallBack() {
//Update here UI element
}
The WorkerDoWork method is executed in a thread that is not the same of the UI.