(just to proof that I understood you correctly) so this means that for my sample I:
a.) can use the "blocked insert"
b.) than I have to call the code shown in your ASPX - for every control contained in the block.
This opens two questions:
a.) Why isn't the Rendermode part of the "UpdatedControl" - since I can (or in my case have to) set it there?
b.) Is it really an "design approach" that adding a block eliminates the setting?
For b.) forget about the need to set the things specific - simply I want to add a "block of controls" (or better described
add an Ajax Setting with multiple Updated Controls).
And this changes the rendering mode (or ignores it) - which I think is not intended.
Conclusion (please correct me if I'm wrong):
My problem having an APSX with "special rendering mode" - can be solved with a script which set's the rendering for every updated control on the proxy.
So I stay independent of the set rendering mode on the "containing page".
--Should be documented somewhere - of much better (if possible) provided as property of "UpdatedControl".
Adding an Ajax setting like in this code
| AjaxSetting aS = new AjaxSetting(aM.ID);
| string strLoadPanelID=aM.DefaultLoadingPanelID; //use default loading panel
| aS.UpdatedControls.Add(new AjaxUpdatedControl(rgBackupFiles.ID, strLoadPanelID));
| aS.UpdatedControls.Add(new AjaxUpdatedControl(hfSaveCurDir.ID,strLoadPanelID));
| aS.UpdatedControls.Add(new AjaxUpdatedControl(hfSaveCurFile.ID,strLoadPanelID));
overrides the UpdatePanelsRenderMode (or at least ignores it) which is a "bug" - or (at least) a "strange behavior" which should be documented.
PS: although the thing with adding an AjaxSetting has a bitter Taste - I thank you very much for the answer since it provides me with a way to have my usercontrols independent of the parents render mode.