Webchart in aspContent usin Masterpage don't Fire ClickEvent

squemeneur · Post by **squemeneur** » Tue Aug 01, 2006 11:48 am

Hello,

I think there is a bug with webchart when you place it in a page ex:Default2.aspx between 2 tags <asp:Content> and use a masterpage.

ClickBackground events and ClickSeries events are not Fired.

Is there a bug ?

This is critical for me.

Thanks

Ps : See my code below

////////////// Default2.aspx ////////////

<%@ Register Assembly="TeeChart" Namespace="Steema.TeeChart.Web" TagPrefix="tchart" %>
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default2.aspx.cs" Inherits="Default2" MasterPageFile="MasterPage.master"%>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentColumn" Runat="server" >
<form id="form1" runat="server">
<div>
<tchart:WebChart ID="WebChart100" style="Z-INDEX: 102; " runat="server" AutoPostback="True" TempChart="Session" Config="AAEAAAD/////AQAAAAUZWVDaGFydAs=" Height="290px" Width="432px" OnClickBackground="WebChart100_ClickBackground" GetChartFile="GetChart.aspx" OnAfterDraw="WebChart100_AfterDraw" />
</div>
</form>
</asp:Content>

////////////// Default2.aspx.cs ////////////

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

public partial class Default2 : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void WebChart100_ClickBackground(object sender, ImageClickEventArgs e)
{
///////is not fired!
}
}

////////////////// MasterPage.master /////
<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>

<!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" >
<head runat="server">
<title>Untitled Page</title>
</head>
<body>

<div>
<asp:contentplaceholder id="ContentColumn" runat="server"></asp:contentplaceholder>
</div>

</body>
</html>
////////////////// MasterPage.master.cs /////

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

public partial class MasterPage : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{

}
}

Post by **Christopher** » Wed Aug 02, 2006 8:06 am

Hello,

Yes, I've been able to reproduce this defect and have fixed for the maintenance release which will become publicly available at the beginning of September.

squemeneur · Post by **squemeneur** » Thu Aug 03, 2006 9:53 am

Thanks for your response.

tridld · Post by **tridld** » Wed Nov 29, 2006 4:57 pm

Has this been fixed yet? I have the same issue.

Narcís · Post by **Narcís** » Thu Nov 30, 2006 9:58 am

Hi tridld,

As Cristopher Ireland said, this was fixed in earlier August, so this should be fixed in all releases since then. Please noticed that some maintenance releases have been posted at the client area since August. Which TeeChart version are you using?

tridld · Post by **tridld** » Fri Dec 01, 2006 3:30 pm

I'm running 1.1.2379.21122 which was the latest on your download site. I noticed it was an August build and that's why I inquired.

Narcís · Post by **Narcís** » Fri Dec 01, 2006 3:48 pm

Hi tridld,

Is AutoPostback set to true for you chart?

tridld · Post by **tridld** » Fri Dec 01, 2006 4:05 pm

Narcís · Post by **Narcís** » Mon Dec 04, 2006 4:20 pm

Hi tridld,

Could you please send us a simple example project we can run "as-is" to reproduce the problem here?

You can post your files at news://www.steema.net/steema.public.attachments newsgroup.

Thanks in advance.

Narcís · Post by **Narcís** » Tue Dec 05, 2006 3:22 pm

Hi tridld,

We could finally reproduce the problem here. It was initially fixed in TeeChart for .NET v2. Now we have fixed it for v1 as well. We expect to post a new version at the client area before Thursday.