UpdatePanelAnimation - all panels animating

Hi,

Love this new control...real easy to use and yet the results are pretty
spectacular.

I know the documentation specifically states that all of the animations will be
played when any update occurs and that this is due to the update panel
architecture.  So, this post is really just a grumble about the limitations of
this architecture.  I have posted about this before (as have others) and this
control is just another demonstration of the limitation of the update panel
architecture.  I think we should be able to have multiple UpdateProgress
controls or animations that can be triggered selectively/independently.  Are
there any plans to enable this?

Thanks,

Jason

hello.

well, to be honest, i really don't think we need multiple updateprogress
controls on a page. what we need is that the updatepanel gets a new
PostbackSettings property which gives us access to the _postbackSettings field
maintained by the class. this would let us know which panel was responsible for
the postback...

Hi Luis,

I still feel there is a need for multiple updateprogress controls because it
would be good to have an animation or text that is displayed near the control
that triggered the postback.  This would give a clear indication of activity
happening in relation to that control.

Building on your example, we could then have multiple updateprogress controls
(located near the control(s) that can trigger a postback) and have them linked
to different updatepanels.  So, when a specific updatepanel triggers the
postback, its linked updateprogress control would activate and provide an
indication of activity in a location that is obvious to the user.

Cheers,

Jason

Hi Jason, you may want to check out this post where I describe how I implemented
a web control which can retrieve the ID of the UpdatePanel which performed the
postback.
http://dotnetslackers.com/community/blogs/simoneb/archive/2006/09/02/Getting-the
-ID-of-the-UpdatePanel-which-triggered-an-asynchronous-postback.aspx

Thanks Simone...it looks like you could some neat stuff with that interception.

I believe that there should be more support for this natively within Atlas
though.  Having different progress indicators in different locations on the page
that get triggered independently is a core requirement for a lot of Ajax
applications.  I am currently compromising by having a single updateprogress
control that is always centred on the page and fairly "in your face"
so that the user can't miss it.

Cheers,

Jason