Hi Telerik,
I have added a BusyIndicator to my main form and have it incapsulating my RadDocking, menu etc.
I works like a charm.
However ;-) - if the user undocks a window before running a 'busy-ecapsulated' function, the undocked window will still be accessible during the long-running function.
Is there a recommended way of handling this situation?
Thanks,
Anders, Denmark
I have added a BusyIndicator to my main form and have it incapsulating my RadDocking, menu etc.
I works like a charm.
However ;-) - if the user undocks a window before running a 'busy-ecapsulated' function, the undocked window will still be accessible during the long-running function.
Is there a recommended way of handling this situation?
Thanks,
Anders, Denmark
1 Answer, 1 is accepted
0
Accepted
Hi Anders,
This is expected behavior since the floated panes are actually popups and are placed above the BusyIndicator. Also the Docking control doesn't know that a busy action is taking place (as this is a custom scenario), so you should manually track the undocked panes and disable them.
We're sorry for the inconvenience.
All the best,
Yana
the Telerik team
This is expected behavior since the floated panes are actually popups and are placed above the BusyIndicator. Also the Docking control doesn't know that a busy action is taking place (as this is a custom scenario), so you should manually track the undocked panes and disable them.
We're sorry for the inconvenience.
All the best,
Yana
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>