TeeChart 2015.15**

TeeChart VCL for Borland/CodeGear/Embarcadero RAD Studio, Delphi and C++ Builder.
Post Reply
kmanuele
Newbie
Newbie
Posts: 11
Joined: Thu Sep 25, 2014 12:00 am

TeeChart 2015.15**

Post by kmanuele » Fri Apr 24, 2015 7:11 pm

Installed the 2015 upgrade for both XE7 and XE8.

Now am getting unresolved external for Vcltee::Teengine::TChartSeries::GetMarks() in an Pie Chart on an existing XE7 project.

Uninstalled, deleted all Tee files, and reinstalled. Didn't help. Verified no *tee* files in Embarcadero folders

Ideas?

Thanks

Kevin

Yeray
Site Admin
Site Admin
Posts: 9612
Joined: Tue Dec 05, 2006 12:00 am
Location: Girona, Catalonia
Contact:

Re: TeeChart 2015.15**

Post by Yeray » Mon Apr 27, 2015 9:16 am

Hello Kevin,

Please check the list of packages and the path libraries.
Then, try if a new simple example project works fine for you.
If a new simple project works fine but not your old application, then I'd check the old project files (with notepad or similar) and manually correct any wrong reference you may find on it.
Best Regards,
ImageYeray Alonso
Development & Support
Steema Software
Av. Montilivi 33, 17003 Girona, Catalonia (SP)
Image Image Image Image Image Image Please read our Bug Fixing Policy

kmanuele
Newbie
Newbie
Posts: 11
Joined: Thu Sep 25, 2014 12:00 am

Re: TeeChart 2015.15**

Post by kmanuele » Mon Apr 27, 2015 7:52 pm

Somehow, my project file had the new TeeChart paths, but they were incomplete. Manually fixed, and all is ok now.

Thanks

Kevin

Yeray
Site Admin
Site Admin
Posts: 9612
Joined: Tue Dec 05, 2006 12:00 am
Location: Girona, Catalonia
Contact:

Re: TeeChart 2015.15**

Post by Yeray » Tue Apr 28, 2015 7:00 am

Hi Kevin,
kmanuele wrote:Somehow, my project file had the new TeeChart paths, but they were incomplete. Manually fixed, and all is ok now.
We'll keep an eye on that. Thanks for the information.
Best Regards,
ImageYeray Alonso
Development & Support
Steema Software
Av. Montilivi 33, 17003 Girona, Catalonia (SP)
Image Image Image Image Image Image Please read our Bug Fixing Policy

Post Reply