I fetch my data and populate the underlying ObservableCollection with the fetched data on a background thread using the TPL, during that time the busy indicator is spinning fine. However, once my data is fetched the ICollectionView my RadDataGird is bound to starts refreshing and the busy indicator freezes until the binding is finished which takes longer than fetching the data and makes the UI look unresponsive...
Now, it makes sense because both the data binding and the busy indicator are running on the UI thread but if that is the case what is the solution to keep the busy indicator spinning during the data binding?
Is there any way to have the busy indicator run on a separate thread?
Now, it makes sense because both the data binding and the busy indicator are running on the UI thread but if that is the case what is the solution to keep the busy indicator spinning during the data binding?
Is there any way to have the busy indicator run on a separate thread?
1 Answer, 1 is accepted
0
Hello,
Thank you for contacting us.
Unfortunately as every other UI control in WPF the BusyIndocator control is rendered in the UI thread and if it is frozen the control will not show.
Currently we are not aware of any workaround to this limitation in the Framework.
If you have any other questions feel free to write to us again.
Regards,
Vladi
the Telerik team
Thank you for contacting us.
Unfortunately as every other UI control in WPF the BusyIndocator control is rendered in the UI thread and if it is frozen the control will not show.
Currently we are not aware of any workaround to this limitation in the Framework.
If you have any other questions feel free to write to us again.
Regards,
Vladi
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.