On my Visual Studio profiler, the following statck is showing up as most expensive, accounting for 17% of total CPU time. This is a real time market data based app.
> Infragisitcs.Windows.DataPresenter.RecordManager.ProcessQueuedChangeNotifications()
> Infragistics.Windows.DataPresenter.RecordManager.OnDelayedChange()
We have our queueing mechanism for propagating propertyChanged notifications to the UI. Is there a way to turn the queueing off inside the XamDataGrid RecordManager from the API?
Thanks.
Hello,
I am just checking your progress on the issue.
If you require any further assistance please do not hesitate to ask .
Sincerely,
Ekaterina
Developer Support Engineer
Infragistics
www.infragistics.com/support
I have been looking into your question and currently the xamDataGrid do not expose a functionality of restricting described mechanism
However there are different approaches in achieving the desired behavior. I have created a sample project that uses the following :
The RefreshCellValue method that refreshes the value of a specified cell. Notice that we do not need to implement INotifyProprtyChange, we can just use a Boolean flag in order to indicate which of the objects in our datasource collection has being updated, then find the corresponding record using its dataItem and call the method.
The second approach includes calling the NotifyPropertyChanged method not on every property change, but again using a flag that indicates if a change in the current instance has been performed. Than we can go through the data source and call NotifyPropertyChanged only on the changed objects.
Please let me know if you require additional assistance regarding the discussed matter.
Infragistics, Inc.