I have a RadUpload control hosted inside a window that wraps everything in a RadBusyIndicator. When the user starts the upload through my command, I make the busy indicator busy and then call StartUpload(). However, StartUpload() is silently short-circuiting. Debugging, I've found my RadUpload.IsEnabled is false, which is a short-circuit condition inside StartUpload().
I found in this other post -- http://www.telerik.com/community/forums/silverlight/busy-indicator/radbusyindicator-and-isenabled.aspx -- that indeed, when a RadBusyIndicator is set to busy -- all of its contents are marked as not enabled (IsEnabled=false).
How can I work around this?
FWIW, I can see RadUpload.UploadCommand wanting to honor IsEnabled since commands are specifically intended to be used with UI controls; however, StartUpload() is a programmatic method that can be triggered any number of ways (such as my case). Why does StartUpload() need to check IsEnabled? Why not let the UploadCommand's CanExecute() honor it but let StartUpload() always load it?
I found in this other post -- http://www.telerik.com/community/forums/silverlight/busy-indicator/radbusyindicator-and-isenabled.aspx -- that indeed, when a RadBusyIndicator is set to busy -- all of its contents are marked as not enabled (IsEnabled=false).
How can I work around this?
FWIW, I can see RadUpload.UploadCommand wanting to honor IsEnabled since commands are specifically intended to be used with UI controls; however, StartUpload() is a programmatic method that can be triggered any number of ways (such as my case). Why does StartUpload() need to check IsEnabled? Why not let the UploadCommand's CanExecute() honor it but let StartUpload() always load it?