UpdatePanel in TabPanel

Coolite Forums

Welcome Guest ( Login | Register )

««1 2

Subscribe
Last Login: Yesterday @ 7:16:50 PM Posts: 648, Posted 8/8/2008 10:03:17 AM Timothy Group: Coolite Premium Member & Early Adopter
Using FF3.0 and cleared everything I can possibly think of I even tried in IE6 which hasn't been running lately, cleared catch ... nadda! Cheers, Timothy ---- Timothy Grant Vogelsang tvogelsang [at] gmail [dot] com Coolite Toolkit 0.7 SVN (Professional Edition) Microsoft .NET Framework 2.0 Microsoft ASP.NET Ajax 1.0 Permalink: Post #1166

Last Login: Yesterday @ 7:16:50 PM Posts: 648, Posted 8/8/2008 10:11:56 AM Timothy Group: Coolite Premium Member & Early Adopter
Found the problem in SVN source code: items.Add("coolite.coolite-ajax.js"); Should be: items.Add(".coolite.coolite-ajax.js"); Line 582 in Coolite.Ext.Web/Core/ScriptManager.cs Cheers, Timothy ---- Timothy Grant Vogelsang tvogelsang [at] gmail [dot] com Coolite Toolkit 0.7 SVN (Professional Edition) Microsoft .NET Framework 2.0 Microsoft ASP.NET Ajax 1.0 Permalink: Post #1167

Last Login: Yesterday @ 7:16:50 PM Posts: 648, Posted 8/8/2008 10:33:32 AM Timothy Group: Coolite Premium Member & Early Adopter
Other than the above, the only other bug I've noticed is when the Tabs do not have an ID. Fails in FF3.0 inside an UpdatePanel. Cheers, Timothy ---- Timothy Grant Vogelsang tvogelsang [at] gmail [dot] com Coolite Toolkit 0.7 SVN (Professional Edition) Microsoft .NET Framework 2.0 Microsoft ASP.NET Ajax 1.0 Permalink: Post #1168

Last Login: Yesterday @ 7:16:50 PM Posts: 648, Posted 8/8/2008 11:20:20 AM Timothy Group: Coolite Premium Member & Early Adopter
The below fails when you switch to the 2nd tab and click "Update": <form id="Form1" runat="server"> <asp:ScriptManager runat="server" /> <ExtJS:ScriptManager runat="server" Theme="Default" /> <asp:UpdatePanel runat="server"> <ContentTemplate> <ExtJS:TabPanel ID="tabsCustomer" runat="server" ActiveTab="0" AutoHeight="True" AutoWidth="True"> <Tabs> <ExtJS:Tab ID="tabCustomerSearch" runat="server" Title="Customer Search" AutoHeight="True" AutoWidth="True"> <Content> <asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="Conditional"> <ContentTemplate> </ContentTemplate> </asp:UpdatePanel> </Content> </ExtJS:Tab> <ExtJS:Tab ID="tabCustomerDetail" runat="server" Title="Customer Detail" AutoHeight="True" AutoWidth="True"> <Content> <asp:UpdatePanel ID="UpdatePanel2" runat="server" UpdateMode="Conditional"> <ContentTemplate> <ExtJS:Button ID="btnUpdate" runat="server" Text="Update" /> </ContentTemplate> </asp:UpdatePanel> </Content> </ExtJS:Tab> </Tabs> </ExtJS:TabPanel> </ContentTemplate> </asp:UpdatePanel> </form> Let me know when you guys want me to test it again -- I'm going to roll back to this mornings copy Cheers, Timothy ---- Timothy Grant Vogelsang tvogelsang [at] gmail [dot] com Coolite Toolkit 0.7 SVN (Professional Edition) Microsoft .NET Framework 2.0 Microsoft ASP.NET Ajax 1.0 Permalink: Post #1169

Last Login: Today @ 12:27:12 AM Posts: 1,644, Posted 8/8/2008 11:46:18 AM geoffrey.mcgill Group: Core Development Team
I'm surprised that that would even work with all native .NET controls. I guess a Parent UpdatePanel with UpdateMode="Always" trumps inner nested UpdatePanels with UpdateMode="Conditional" even when the .update is triggered from the "Conditional" UpdatePanel. Seems like if any Parent UpdatePanel in the stack is set to "Always", every Child is always updated, even when the Child is specifically set to "Conditional". Kinda makes setting "Conditional" pointless on child <asp:UpdatePanel>'s if a Parent does not follow the same pattern. I guess it's "all or none". I'll modify the logic to always update Toolkit Controls if a Parent UpdatePanel is set to "Always". Should be a quick fix. Setting the first <asp:UpdatePanel> to UpdateMode="Conditional" in your latest example above should fix the error, which is also how your original sample was configured. Hope this helps. -- Geoffrey McGill Coolite Inc. Development Team Coolite Examples \| Coolite API Docs \| ExtJS API Docs twitter [coolite \| personal] Permalink: Post #1170

Last Login: Yesterday @ 7:16:50 PM Posts: 648, Posted 8/8/2008 12:07:18 PM Timothy Group: Coolite Premium Member & Early Adopter
You're absolutely correct with the outer UpdatePanel always updating the inner UpdatePanels even when Conditional, my mistake. The only real problem I have right now is the IDs missing on controls within a TabPanel inside an UpdatePanel. This is generating corruption errors in FF3.0. Oh, and if you could commit the '.' missing in SVN that would be ace; I hate working with a modified copy of something Cheers, Timothy ---- Timothy Grant Vogelsang tvogelsang [at] gmail [dot] com Coolite Toolkit 0.7 SVN (Professional Edition) Microsoft .NET Framework 2.0 Microsoft ASP.NET Ajax 1.0 Permalink: Post #1171

Last Login: Today @ 12:27:12 AM Posts: 1,644, Posted 8/8/2008 12:10:38 PM geoffrey.mcgill Group: Core Development Team
I took a look at the missing ID's, although can not seem to reproduce yet. I'll keep looking. I'm sure it's a problem of referencing the .ID or .ClientID property instead of the .UniqueID property when doing lookup's on the controls. The '.' revision was committed approx 30 minutes ago. Hope this helps. -- Geoffrey McGill Coolite Inc. Development Team Coolite Examples \| Coolite API Docs \| ExtJS API Docs twitter [coolite \| personal] Permalink: Post #1172