[CLOSED] Coolite Ext TabPanel Not Working

Printable View

Jul 19, 2010, 8:45 PM
LeeTheGreek

[CLOSED] Coolite Ext TabPanel Not Working

Hi,

I have a coolite tabpanel enclosed within a coolite panel control. When i click on a tab, the following javascript error occurs: Microsoft JScript runtime error: 'disabled' is null or not an object. Any help to resolve this problem would be much appreciated.

Many Thanks

Lee

Code:

<ext:Panel ID="_panel1" runat="server" Frame="true" Border="true" Height="420" Collapsible="true" AllowDomMove="true"> <Content> <ext:TabPanel ID="_tabPanel1" runat="server" AutoHeight="true" Border="true" AutoWidth="true" EnableTabScroll="true" StyleSpec="padding-top:1px;"> <Items> <ext:Panel ID="_tab1" runat="server" Title="Tab1"> </ext:Panel> <ext:Panel ID="_tab2" runat="server" Title="Tab2"> </ext:Panel> <ext:Panel ID="_tab3" runat="server" Title="Tab3"> </ext:Panel> </Items> </ext:TabPanel> </Content> </ext:Panel>
Jul 19, 2010, 8:57 PM
Vladimir

Hi,

I cannot reproduce it. Please provide full test sample

P.S. Please use Fit layout instead AutoWidth/AutoHeight properties (it will produce better result)

Code:

<ext:Panel ID="_panel1" runat="server" Frame="true" Border="true" Height="420" Collapsible="true" AllowDomMove="true" Layout="Fit"> <Items> <ext:TabPanel ID="_tabPanel1" runat="server" Border="true" EnableTabScroll="true" StyleSpec="padding-top:1px;"> <Items> <ext:Panel ID="_tab1" runat="server" Title="Tab1"> </ext:Panel> <ext:Panel ID="_tab2" runat="server" Title="Tab2"> </ext:Panel> <ext:Panel ID="_tab3" runat="server" Title="Tab3"> </ext:Panel> </Items> </ext:TabPanel> </Items> </ext:Panel>
Jul 19, 2010, 8:59 PM
geoffrey.mcgill

Hi,

The code sample you provided does not appear to reproduce the problem.
Jul 20, 2010, 10:36 AM
LeeTheGreek

Hi,

I will attach a sample project later today, in the meantime i have another question that might be related. If i download the latest version of Ext.Net and include it within my project (vs.net 2008). When i run my project it throws an error within Ext.Net.StateManagedItem, line 109 - NullReferenceException:

Code:

internal void RegisterDataBinding() { this.ResourceManager.Page.PreRenderComplete += this.DataBindPoint; }

The only way i could resolve the problem was to comment out line 109. Do you think this is why the tabs aren't quite working? And on a separate note why is it throwing an error in the first place

Cheers

Lee
Jul 20, 2010, 12:27 PM
Vladimir

Hi,

What is null in that line? ResourceManager or ResourceManager.Page? Where is the ResourceManager located? Inside ASP.NET form or outside?

Can you provide test case which demonstrates that exeption?
Jul 21, 2010, 8:15 AM
LeeTheGreek

ResourceManager is null. It is located within the asp.net form. This used to work fine until i upgraded to the latest version of Coolite. Below is the sample masterpage i am playing with.

Code:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title></title> <style type="text/css"> /* css class that specifies background image to be used as the icon image: */ .my-icon2 { background-image: url("/images/icon.png") 0 6px no-repeat !important; } </style> <script type="text/javascript"> function createWindow(title, description) { var window = new Ext.Window({ title: title, html: description, modal: true, layout: 'fit', closable: true, collapsible: true, animCollapse : true, iconCls: 'my-icon2', bodyStyle: 'padding: 6px; background-color: #fff;', width: 400, height: 200 }); window.show(); } </script> <meta http-equiv="Content-Language" content="en" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta http-equiv="X-UA-Compatible" content="IE=8" /> <base target="_self" /> </head> <body> <form id="form1" runat="server"> <asp:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true"></asp:ScriptManager> <ext:ResourceManager ID="ScriptManager2" runat="server" Theme="Gray" InitScriptMode="Inline" CleanResourceUrl="false" ScriptMode="Debug"></ext:ResourceManager> <asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="Conditional"> <ContentTemplate> <asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server"></asp:ContentPlaceHolder> </ContentTemplate> </asp:UpdatePanel> </form> </body> </html>
Jul 21, 2010, 8:21 AM
macap

Hi,

to come to your initial problem. Only some ideas...

Quote:

Originally Posted by LeeTheGreek

Code:

<asp:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true"></asp:ScriptManager> <ext:ResourceManager ID="ScriptManager2" runat="server" Theme="Gray" InitScriptMode="Inline" CleanResourceUrl="false" ScriptMode="Debug"></ext:ResourceManager>

Did you try your problem without master page?

If that works fine then:

a. Did you try your initial problem without the asp-Scriptmanager?

AFAIK I remember deep in my mind, that it´s better to add the ext-ResourceManager before the asp-ScriptManager.

b. move the ext-ResourceManager Control above the ScriptManager Control

c. Do a test without InitScriptMode="Inline".

Good luck,

Martin
Jul 21, 2010, 9:36 AM
Vladimir

Hi,

Unfortunately, your code doesn't reproduce the problem. Can you create simple test project, zip it and post (without any assemblies)?
Jul 24, 2010, 1:50 PM
LeeTheGreek

Hi,

Below is a link to the sample project. Apologies for it not being an attachment. The upload tool kept hanging.

Regards

Lee
Jul 26, 2010, 10:47 AM
Vladimir

Hi,

The problem is related with underscore in the Tabs' ids and TabPanel's ID (ASP.NET adds second underscore to the ClientID, but tab panel uses double underscore as id delimiter)
If you remove those underscores then exception is gone
Or add the following custom config to the TabPanel

Code:

<ext:ConfigItem Name="idDelimiter" Value="$$" Mode="Value" />

P.S.

Quote:

When i run my project it throws an error within Ext.Net.StateManagedItem, line 109 - NullReferenceException:

internal void RegisterDataBinding()
{
this.ResourceManager.Page.PreRenderComplete += this.DataBindPoint;
}

Your test sample doesn't reproduce that problem