I have a XamDataGrid that requires a converter in the binding, due to the fact that one of the fields is a drop-down based off of a previously user selected value in the same grid. This forces the grid to call my IValueConverter for each record, and i have many records. I already have a busy indicator that displays while the acutal data is loaded into the grid etc. Problem is it is apparently blocked while the converter is called 295 times (for ach record). How can i keep my busy indicator from freezing because of this?
Hello Travis,
I am just checking if you require any further assistance on the matter.
I have been looking into this issue and this behavior cannot be prevented when updating the mouse indicator on the UI thread. I believe that there is no event that fires every time when any action of XamDataGrid requires more time to complete. In my opinion this issue is caused by the approach that you use to retrieve the data from your data base.
Let me know, if you have any other questions on this matter.
the sleep is to simulate my call to SQL
Hi Travis,
I have been looking into your sample application and I am not sure why you are putting the thread to sleep in the converter because it seems that there is no need and this make the application freezes.
There is no way to invoke the converter only for some particular records in your scenario as it is applied every record.
My suggestion is to remove the Sleep method:
Thread.Sleep(100);
Let me know, if you need any further assistance on this matter.
attached is a sample showing the problem i am experiencing. how can i keep the wait cursor from showing numerous times, for example, when scrolling or grouping/ungrouping. i wish it to show once when ungrouping, instead of each time the converter is hit.