Hi!
there are several occasions that the controls do not behave instantly, depending also on the performance capabilities of the current machine and the complexity of the UI.
I see this for instance when expanding/collapsing rows in the RadTreeListView, or expanding/collapsing the RadExpander. Another example is when my user clicks on a grid row and the grid has to switch the display to the editing template of the corresponding column. The same when the user expands a pane in the RadDocking control.
By default these controls do not switch the cursor to the wait cursor, so if these operations take a second to complete, there is no indication that they even have started. So the user tends to click again and again, resulting in strange behavior depending on the occasion.
I'm interesting in just replacing the Arrow cursor with the WaitCursor and not something more complex like using the RadBusyIndicator.
Any solution?
there are several occasions that the controls do not behave instantly, depending also on the performance capabilities of the current machine and the complexity of the UI.
I see this for instance when expanding/collapsing rows in the RadTreeListView, or expanding/collapsing the RadExpander. Another example is when my user clicks on a grid row and the grid has to switch the display to the editing template of the corresponding column. The same when the user expands a pane in the RadDocking control.
By default these controls do not switch the cursor to the wait cursor, so if these operations take a second to complete, there is no indication that they even have started. So the user tends to click again and again, resulting in strange behavior depending on the occasion.
I'm interesting in just replacing the Arrow cursor with the WaitCursor and not something more complex like using the RadBusyIndicator.
Any solution?