Getting TeeChart for .NET to work with Delphi 2006 and ASP.NET is easy enough. However, edits made to the chart style and data at design time do not persist to runtime. With VS 2003, chart styles and data do persist.
Is there a way to configure the chart at design time and have the data available at runtime using Delphi 2006 for ASP.NET? Or, with Delphi is it necessary to define the chart style and data only using runtime code?
On a related note, how is this data being persisted in VS 2003 with C#? It doesn't appear to be defined using InitializeComponent.
Thanks in advance
TeeChart data and Delphi 2006 for ASP.NET vs VS 2003
-
- Site Admin
- Posts: 14730
- Joined: Mon Jun 09, 2003 4:00 am
- Location: Banyoles, Catalonia
- Contact:
Hi GregS,
TeeChart for .NET is being serialized in InitializeComponent's method implementation, in the Windows Form Designer generated code section. Can't you find this in your projects?
This is a known issue (TF02011193) which need to be investigated for future releases. In the meantime, the only way is setting chart at run-time.Is there a way to configure the chart at design time and have the data available at runtime using Delphi 2006 for ASP.NET? Or, with Delphi is it necessary to define the chart style and data only using runtime code?
On a related note, how is this data being persisted in VS 2003 with C#? It doesn't appear to be defined using InitializeComponent.
TeeChart for .NET is being serialized in InitializeComponent's method implementation, in the Windows Form Designer generated code section. Can't you find this in your projects?
Best Regards,
Narcís Calvet / Development & Support Steema Software Avinguda Montilivi 33, 17003 Girona, Catalonia Tel: 34 972 218 797 http://www.steema.com |
Instructions - How to post in this forum |
Looked at it again. Nothing TeeChart specific in InitializeComponent in C# (only an event handler assignment at this time).
I looked at the ASPX and the data seems to be persisted using encoded text in the Config attribute of the tchart:WebChart element. I was hoping that I could inspect the property assignments to gain insight into which properties I needed to set programmatically in Delphi. Oh, well.
Thanks for the reply.
On a side note, while setting the properties programmatically is not all that convenient, with so many Delphi developers are already familiar with your product, I don’t understand why you don’t promote the Delphi use of TeeChart for .NET (or really even mention it for that matter). Our development team couldn’t certify that it could be used in Delphi until we tried it (though we were pretty sure that it would be possible). I think you’re missing a fairly good size market.
I looked at the ASPX and the data seems to be persisted using encoded text in the Config attribute of the tchart:WebChart element. I was hoping that I could inspect the property assignments to gain insight into which properties I needed to set programmatically in Delphi. Oh, well.
Thanks for the reply.
On a side note, while setting the properties programmatically is not all that convenient, with so many Delphi developers are already familiar with your product, I don’t understand why you don’t promote the Delphi use of TeeChart for .NET (or really even mention it for that matter). Our development team couldn’t certify that it could be used in Delphi until we tried it (though we were pretty sure that it would be possible). I think you’re missing a fairly good size market.
-
- Site Admin
- Posts: 14730
- Joined: Mon Jun 09, 2003 4:00 am
- Location: Banyoles, Catalonia
- Contact:
Hi GregS,
Sorry, I forgot you were speaking about WebForms applications. In WebForms applications WebChart is serialized in the WebForm's HTML code in a tchart:WebChart tag and its Config property.
Sorry, I forgot you were speaking about WebForms applications. In WebForms applications WebChart is serialized in the WebForm's HTML code in a tchart:WebChart tag and its Config property.
Thanks you very much for your suggestion. I ignore if there's a technical cause for that but I'll pass your comment onto my colleagues.On a side note, while setting the properties programmatically is not all that convenient, with so many Delphi developers are already familiar with your product, I don’t understand why you don’t promote the Delphi use of TeeChart for .NET (or really even mention it for that matter). Our development team couldn’t certify that it could be used in Delphi until we tried it (though we were pretty sure that it would be possible). I think you’re missing a fairly good size market.
Best Regards,
Narcís Calvet / Development & Support Steema Software Avinguda Montilivi 33, 17003 Girona, Catalonia Tel: 34 972 218 797 http://www.steema.com |
Instructions - How to post in this forum |
-
- Newbie
- Posts: 5
- Joined: Wed Jun 28, 2006 12:00 am
-
- Site Admin
- Posts: 14730
- Joined: Mon Jun 09, 2003 4:00 am
- Location: Banyoles, Catalonia
- Contact:
Hi Dave,
It is most unlikely that this gets fixed as CodeGear announced that they don't plan to further develop nor support Delphi for .NET technology.
Also please notice that even that was fixed not much could be done in WebForms at design-time because because WebForms are stateless. For example, in Visual Studio .NET, little can be done at design-time with WebChart, most settings must be done at run-time.
It is most unlikely that this gets fixed as CodeGear announced that they don't plan to further develop nor support Delphi for .NET technology.
Also please notice that even that was fixed not much could be done in WebForms at design-time because because WebForms are stateless. For example, in Visual Studio .NET, little can be done at design-time with WebChart, most settings must be done at run-time.
Best Regards,
Narcís Calvet / Development & Support Steema Software Avinguda Montilivi 33, 17003 Girona, Catalonia Tel: 34 972 218 797 http://www.steema.com |
Instructions - How to post in this forum |