Hello,
I've two problems regarding the RadWaitingBar
- using it with an AssociatedControl it takes "ages" for the waitbar to show up
Simple form with some panels ans some inputs the waitbar takes about 1 second to show, (less controls = faster)
- in some cases theres an exception if an underlaying control gets disabled before the waitbar is shown
both problems can be recreated/tested with the attached project (zip)
Kind regards
Christian
4 Answers, 1 is accepted
Thanks for the project.
1. The time is 0.5 seconds on my side and the waiting bar just flashes on the screen. What is the result on your side?
2. There is no exception on my side. The attached video shows how I am testing this. Am I missing something? Can you share the StackTrace of the exception as well?
Thank you in advance for your patience and cooperation.
Regards,
Dimitar
Progress Telerik
Rank 1
Hi Dimitar,
1. Even .5 seconds is way to long. It dosen't matter how long the WaitBar is shown it's about the time for the StartWaiting() call. I guess you'r hardware isn't that bad, so most consumer/client PCs aren't that good. I didn't measure it, but if it takes about 1 second on my setup it'll take way more on the clients. And everything above .25 seconds is human noticeable. It takes less than .5 seconds for the complete form to load, so displaying a overlay and the WaitBar shouldn't take longer.
2. You should enable the CLR exceptions in VS or you can add a breakpoint in RadForm3 line 44 (try/catch block).
Rank 1
Hi Dimitar,
- Even .5 seconds is to slow (everything longer than .25 seconds is human noticeable). It's not about how long the WaitBar is visible, it's about how long it takes for the StartWaiting() call. If it takes 1 second on my setup it'll take way longer on the client PCs.
It takes about .5 seconds for the complete form to load, so it shouldn't take the longer to do the overlay and display the WaitBar.
- If you enable the CLR exceptions in VS or add a breakpoint in RadForm3 line 44 then you'll get the exception
We have further investigated both cases.
1. What causes the delay is creating a bitmap of the underlying control. The process can be improved and this is why I have logged this in our Feedback Portal. You can track its progress, subscribe to status changes and add your comment to it here.
Unfortunately, I cannot suggest a workaround for this case.
2. The exception is caused because the associated control is disabled. I have logged this issue as well. You can track its progress, subscribe to status changes and add your comment to it here.
To work around it, you can enable the control while showing the waiting bar.
Should you have any other questions do not hesitate to ask.
Regards,
Dimitar
Progress Telerik