Teechart Pro is no translatable with ITE delphi !!!!

TeeChart VCL for Borland/CodeGear/Embarcadero RAD Studio, Delphi and C++ Builder.
Post Reply
MD
Newbie
Newbie
Posts: 20
Joined: Mon Jan 30, 2006 12:00 am

Teechart Pro is no translatable with ITE delphi !!!!

Post by MD » Mon Oct 23, 2006 12:47 pm

:evil:

Hi,

I work actually with D2005 update 3 and Teechart Pro VCL 7.05

I have still PB for translate my programme with ITE borland and Teechart dfm reférence.

I find dfm. I rename dfm , I order Techart with source but no result !!!!

The main Error is in editor chart with "Error class no found" at runtime EditiChart(Chart1).

Why do not solution with borland ???
Why Error class no found ???

I'm very tired, plesae is very urgent for me.

Narcís
Site Admin
Site Admin
Posts: 14730
Joined: Mon Jun 09, 2003 4:00 am
Location: Banyoles, Catalonia
Contact:

Post by Narcís » Mon Oct 23, 2006 3:55 pm

Hi MD,

The problem is ITE library still thinks you're using old Teechart version (it included AreaEdit.dfm form). As of TeeChart v7 all TeeChart specific forms/units start with Tee*.dfm(pas). In your case AreaEdit.dfm has been replaced with TeeAreaEdit.pas(dfm) unit. The problem is ITE is looking for old AreaEdit.dfm form which is no longer available.

The solution would be to:

a) remove references to old Teechart forms in ITE library

b) add references to new TeeChart forms.

Now, the problem is I'm not sure how you can do step (a). The best thing to do is check with Borland what they have to say about this one (how to remove references to standard Teechart forms).

Alternative solution is to use our own translation tool we introduced in TeeChart 5.02 release. Selecting language is quite easy. To include different language translations to single distribution, do the following:

1) Include all languages you want to use + three more units in the Uses
section:

Uses TeeConst, TeeProCo, { <-- English }
{ Languages }
TeeFrench, TeeGerman, TeeSpanish,
TeeTranslate; { Translation system }

2) In code change to different language by TeeSetXXX (XXX=language) call.

3) In case you're building with the runtime packages, you'll also have to
include the TeeLanguage79.bpl package to your distribution.
Best Regards,
Narcís Calvet / Development & Support
Steema Software
Avinguda Montilivi 33, 17003 Girona, Catalonia
Tel: 34 972 218 797
http://www.steema.com
Image Image Image Image Image Image
Instructions - How to post in this forum

MD
Newbie
Newbie
Posts: 20
Joined: Mon Jan 30, 2006 12:00 am

Post by MD » Tue Oct 24, 2006 12:24 pm

solution A:
Borland is silent in this case for the moment !!

Solution B
you do not remove the PB, because ITE continue with reférence .ENG projet and my application include all compilation for one file exe.


No the solution for the good job is you provide how remove the référence OLD teechart v4 in ITE, is your component....

MD
Newbie
Newbie
Posts: 15
Joined: Tue Jun 28, 2005 4:00 am
Location: France

Post by MD » Thu Oct 26, 2006 8:27 am

I am in contact with Borland.
Technical support say me : "I'm not sure if a third party component (TeeChart version 7 components) will work with Delphi 2005."

I describe the problem in detail to them.

Do you have arguments (which I communicate to them) to prove the compatibility of the TeeChart components?

Narcís
Site Admin
Site Admin
Posts: 14730
Joined: Mon Jun 09, 2003 4:00 am
Location: Banyoles, Catalonia
Contact:

Post by Narcís » Fri Oct 27, 2006 10:56 am

Hi MD,

Please see my reply at your other message.
Best Regards,
Narcís Calvet / Development & Support
Steema Software
Avinguda Montilivi 33, 17003 Girona, Catalonia
Tel: 34 972 218 797
http://www.steema.com
Image Image Image Image Image Image
Instructions - How to post in this forum

MD
Newbie
Newbie
Posts: 15
Joined: Tue Jun 28, 2005 4:00 am
Location: France

Post by MD » Fri Nov 10, 2006 8:23 am

A SysOp of Borland's Quality Central says me :

"Otherwise, the only thing I can recomment is to change the class names of all TeeChart forms (e.g. by prefixing them all wiith TeePro or something similar). That obviously will affect a lot of source code, but that will at least solve the problem with ITE getting in your way."

Do you think this solution will be work ?

Post Reply