In my case I don't use loading panel for AJAX requests. I use it as loading image animation. From client code I update img->src and show loading panel as it is described here:
http://www.telerik.com/help/aspnet-ajax/ajxshowhideloadingpanel.html
The only difference that I use it out ajax request.
After image is loaded (onload event) I hide panel.

It is displayed correctly if InitialDelayTime is set to 0. And doesn't being displayed at all if InitialDelayTime is not 0.
Regarding my investigation it happens by design.
Please confirm that I'm right.

Thank you.

PS: if you know more rational way to show loading animation while getting big images, please share it here :)

• 100% Ajax - No flickering
• Ability to retrieve the value of a textbox via server side code
• Ability to close the window after saving or canceling
• Ability to reopen window to add / edit additional data after closing window
• Ability to set the value of a textbox in the form when editing

Currently the following works:

• Retrieve the value of a textbox via server side code
• Can close the window if content template does not contain a Rad Ajax Panel. (Rad Ajax Panel is the only way I have found to  prevent screen flicker when clicking Save / Cancel buttons)
• If window is closed, clicking button to reopen it does not work

Any advice, help, sample code would be appreciated.

Thanks,

Lonnie

[UPDATE]  I have attached an image highlighting the error.

THanks.

[Original message below] 

I am using the Inline Edit Mode of the radgrid.  When I enter Edit mode, the images for the control cannot be located.  For example, when I click the "Add New Record" link,  the "BreakStartTime" control displays "Open the time view popup" instead of showing the image for the time picker. 

Here is a code snippet:

Any thoughts of what I can look for?

Thanks.
Steve

I have a very simple example below but am getting confusing results.  I was hoping that somebody could help me understand what is happening and how to get the desired results.

I have a RadAjaxManager configured so that an ASP.NET Button's click event updates a div (containing a label), with a corresponding RadAjaxLoadingPanel.

The button's server side click event looks like this:

Currently I have the RadAjaxManager's 'RequestQueueSize' property set to 0, the default.  I want to keep it this way so that if a 2nd request occurs before the 1st request's response returns, that 1st request will be cancelled and the 2nd request will be sent.

This is occuring, however, when you click the button twice within that five second wait, two undesrable things happen that I would not have expected to happen.

1. The loading panel disappears on the 2nd click, even though the 2nd request is still processing.  I would like it to stay until the response from the 2nd click returns so that the user knows their 2nd request is still processing.  I have even tried forcing this behavior myself using the RadAjaxManager's 'OnRequestStart' and 'OnResponseEnd' client events (with the help of Telerik documentation) but was not able to get the loading panel to remain for both clicks within the 5 seconds.  Question: How can I get the loading panel to stay until the 2nd request's response returns?  Do I have something configured wrong? Note: I did notice that if I increase the RadAjaxManager's 'RequestQueueSize' that a loading panel remains until the last request's response returns, but unfortunately I need the RequestQueueSize set to 0.
2. I notice that the order of events for the RadAjaxManager is slightly confusing.  I have some client-script that writes out to the screen every time the 'OnRequestStart' and 'OnResponseEnd' events get fired.  When I click the button twice within the five second wait, I see that these events get called in the following order:

• OnRequestStart
• OnRequestStart
• OnResponseEnd
• OnResponseEnd
• OnResponseEnd

    Question: Why does the OnResponseEnd get called three times?  Note: if you continue to click the button more than twice, the 'OnResponseEnd' event gets called even more times.

Here is my aspx markup.  The javascript just writes which events were fired into a div at the bottom of the screen.  The two styles are included to better display what is happening.

I look forward to understanding what is happening here.  Thank you for your help!
--Jason