Hello,
I'm using your RadGridView with the DataLoadMode on Async. What I've noticed is that the DataLoadMode cause the filters etc to be really unstable. However, the DataLoadMode on async makes the application really good, as it doesn't hang up the UI thread. But this won't work as long as it
Right now I'm using the your RadGridView and search bar from the Outlook Template (found here: https://docs.telerik.com/devtools/winforms/visual-studio-integration/visual-studio-templates) . I'm working with large data sets, so upon search and loading of data, it freezes the UI Thread.
I'm wondering how can I make the filtering and search etc to have the same async behavior as the dataloadmode async?
I also noticed that after using the search bar, the busyindicator for like data loading when I click on a button to show data e.g. etc stops working.
8 Answers, 1 is accepted


We don't recommend setting the DataLoadMode to Asynchronous. This could lead to issues as the ones you experience with the filtering. I will guess setting the mode to Synchronous will resolve the filtering issue you mentioned in your last reply. However, if it doesn't I would ask you to isolate it in a project and open a new support ticket from your telerik.com account.
Regards,
Martin Ivanov
Progress Telerik

To achieve an async data loading you can use a BackgroundWorker or a similar approach for loading the data on a background thread, and then assign it to the RadGridView control. Then you can use its IsBusy property to show a busy indicator while the data is loading. As for an async searching and filtering, I am afraid that the RadGridView control doesn't provide support for this.
Regards,
Martin Ivanov
Progress Telerik


I attached a small example showing how to use the busy indication support. However, keep in mind that this is useful if you need to wait some time to generate or fetch your data (for example from a remote data service). However, the operations related to the RadGridView control, like setting its data source or filters cannot be created async or busy indicated. This is because of the nature of the WPF framework. Basically, everything related to the UI happens on a single thread. You can read some more about this in MSDN.
I could recommend to prepare a runnable example that shows your exact set up and the observed issues and then open a new support ticket from your telerik.com account. There you can attach the project and we can think if there is some specific optimizations to suggest.
Regards,
Martin Ivanov
Progress Telerik