Thank you! I was able to follow the same line of reasoning that you described, except using the object model of the 3rd party control I am using.

Good stuff!!

Why don’t you integrate this into the AJAX control toolkit? This is good concept and the masses should get this with a simple download of the AJAX control toolkit.

Hi, it’s a great extender, but can you also support the linkButtons? I’d appreciate if I could also see the source code…

For those of us not using Visual Studio, what does the Assembly registration look like for your control?

Dave

This extender is great! But I think I might have found a bug. I’m trying to use it with an ImageButton, and it seems that the WaitImageURL property isn’t acting as intended. I debugged with FireBug and found this code:

_partialUpdateBeginRequest : function(sender, e)
{
$get(e._postBackElement.id).disabled = true;

if (e._postBackElement.type == “submit” && this._WaitTextValue != “”)
{
this._oldValue = $get(e._postBackElement.id).value;
$get(e._postBackElement.id).value = this._WaitTextValue;
}
else if (e._postBackElement.type == “image” && this._WaitImageURL != “”)
{
this._oldImageURL = $get(e._postBackElement.id).src;
$get(e._postBackElement.id).src = this._WaitImageURLValue;
}
}

Should that else if contain (e._postBackElement.type == “image” && this._WaitImageURLValue != “”) instead? this._WaitImageURL is undefined while this._WaitImageURLValue matches up with the WaitImageURL property.

Updated to version 0.8.

Massive changes this version, including removal of the Toolkit dependency and properly being able to target only certain UpdatePanels.

Give it a try and let me know what you think.

Is that possible to use imagebutton within monitored update panel like:

I tried this but it’s not working. If I remove the monitoredupdatepanel, it works like a charm. Any idea?
Thanks,

Updated to version 0.9. The new version adds a couple new features and a couple bugfixes, thanks to Chris’ feedback. Thanks, Chris!

Support for LinkButtons would be great.

Hi,

args.get_postbackBackElement() can return null in which case asking for the type gives a null reference (using v0.9)

And so can sender._postBackSettings.sourceElement

Excellent, works great right out of the box Thanks!

Hi the ajax control toolkit is updated.
thanks for attention.

Dave, any plans to release the source or add support for LinkButton. We use as many link buttons as regular ones. Thanks!

Dave, the control works fine, however, when in design view, the controls on the page do not render and an error is displayed. It reads, “Error Creating Control - Content1 ‘encosia:PostBackRitalin’ could not be set on property ‘MonitoredUpdatePanels’.

This isn’t a problem for me, but the designers on my team are complaining. Do you know what is causing this. This is within a master page. Thanks!

Do you have any plans to implement “Sorting” on gridviews?

Example, I have a search form. Clicking the button triggers the event, but columns sorting does not trigger this to lock the button.

Do you have any instructions on how to do this or plans to implement this into the control?

Nice work so far.

I have a problem with the new CSS cursor changes in 0.9. On a button click, if the code being called in the button click event handler and an exception is thrown I would like the user to be able to click the button again (i.e. it returns to its original state). At the moment the text reverts and button becomes enabled, but the cursor does not change back to an arrow and remains an hourglass.

Long story short, is it possible to remove this change
Added CSS to change cursor style to “wait” when hovering over the disabled control.
or at least provide a way to disable it?

When is the next version to be released?

I have noticed another issue. I have a set of navigation buttons to navigate through pages of an asp:MultiView. The next button is disabled on the last page, and the previous button is disabled on the first page. When the Postback Ritalin extender is applied, the enabled state is overriden with true. i.e. The next/previous buttons are always enabled after clicking on them once. Obviously, a workaround would be to put them in a separate update panel, but its not exactly elegant.

Beautiful control, thank you!

One question… is there a way to set the Wait text in the codebehind? I need to change it programmatically as my website is localized so the text should be multilingual as well.

Thanks a lot!
Radoslav

I’ve encountered an error caused by the fact that you check for the existence of a control before checking to see if the panel is monitored. Specifically the line of code in the EndRequest handler, PBR_EndRequest(sender, args), and is

if ($get(sender._postBackSettings.sourceElement.id) != null && PBR_IsMonitoredRequest(sender._postBackSettings.panelID))

I have a GridView and when I add default pager controls, they are implemented as <input type=”image”….> having no ID. The $get method throws an exception because the ID defaults to “” and $get fails on this. The GridView is an update panel that is not monitored by PBR, so if the conditional components were switched I don’t think the error would occur. Better yet, make sure that ID is not empty and null before calling $get. Unfortunately without the code, I’m stuck and can’t use the control (which I really like) on the page.

Thanks,
Richard