You searched for the word(s): userid:641155

More Search Options

RSS Available

• Re: how to get which UpdatePanel has posted

  Cyril, Yeah, you're right. Good catch. I'll tweak on it some more as the need arises. Thanks! Eric

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by ewlloyd on 12/26/2006

• Re: how to get which UpdatePanel has posted

  My apologies, Cyril. I didn't get a really good look at your code before posting. You do seem to have the problem covered pretty well. One thing neither of us handles quite right is the case where a single control might trigger the update of multiple panels. Still, does anyone else find it just a bit crazy that we have to go to this monumental effort just to determine which panels are being updated? There should be a better way. Cheers! Eric

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by ewlloyd on 12/22/2006

• Re: how to get which UpdatePanel has posted

  Gents, Actually, it gets worse. Both code blocks above make the assumption that the triggering AsyncPostBackSourceElementID is a child of the UpdatePanel in question. This is by no means a safe assumption. External triggers could set it off. The only way I can see to ensure that you've unequivocally determined which UpdatePanel is being processed is to iterate the UpdatePanels (for which there is no simple method), iterate their triggers (which have to be cast either to PostBackTrigger or AsyncPostBackTrigger

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by ewlloyd on 12/22/2006
  Filed under: updatepanel, "AsyncPostbackTrigger", "Using UpdatePanel", ajax

• Re: Bug: CascadingDropDown: SelectedValue returns garbage from client

  Found the bug-tracker. It's posted as Work Item #5821 over at CodePlex.

  Posted to ASP.NET AJAX Control Toolkit (Forum) by ewlloyd on 11/27/2006

• Re: Bug: CascadingDropDown: SelectedValue returns garbage from client

  David, If the intended usage is to use the DropDownList.Selected... accessors, why put those public accessors on the CascadingDropDown in the first place? Actually, the DropDownList accessors were my first attempt -- it doesn't work. You can't safely Bind() to the DropDownList.SelectedValue under a CascadingDropDown. It chokes when Bind() tries to wedge a SelectedValue in that doesn't exist in the Items collection (pretty much always, given that the dropdown is populated on the client side). The

  Posted to ASP.NET AJAX Control Toolkit (Forum) by ewlloyd on 11/21/2006

• Bug: CascadingDropDown: SelectedValue returns garbage from client

  Greetings, I'm implementing a site that presents a ReorderList with three CascadingDropDowns on it. I'm using the latest beta (September). After much wailing and gnashing of teeth, I finally got the idea that you Bind() the SelectedValue on the CascadingDropDown, not the DropDown. However, it gets better. Where the binding logic was inserting a value of, say, "18" for the SelectedValue, the client code was returning a value of "18::: Name Of Selection As It Appears In The Dropdown " (or "18:::undefined

  Posted to ASP.NET AJAX Control Toolkit (Forum) by ewlloyd on 11/7/2006
  Filed under: bug, CascadingDropDown, SelectedValue