![]() | Steema Issues DatabaseNote: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;otherwise you can use StackOverflow. Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy. |
| Summary: | Code doesn't compile | ||
|---|---|---|---|
| Product: | VCL TeeChart | Reporter: | g.h.m.laagland |
| Component: | Install | Assignee: | Steema Issue Manager <issuemanager> |
| Status: | RESOLVED NOTABUG | ||
| Severity: | blocker | CC: | g.h.m.laagland, narcis, yeray |
| Priority: | Highest | ||
| Version: | 140512 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows | ||
| Chart Series: | --- | Delphi / C++ Builder RAD IDE Version: | RAD XE6 |
| Attachments: |
Screen dump showing the installed packages
Compiler shows assumed error Screendump of programs folder |
||
Created attachment 284 [details]
Compiler shows assumed error
Created attachment 285 [details]
Screendump of programs folder
Please try compiling the code using supplied Recompile tool. It will generate missing FMXTee or VCLTee prefixed units. I think you don't have TeeChart sources so you can't use TeeRecompile. Does a new project with just a TChart on the form work fine for you? - If not, please try reinstalling the component (you can run TeeInstall twice) and check the paths in the IDE. - If yes, but your old project still fails, please check the paths both in the IDE and in the project. |
Created attachment 283 [details] Screen dump showing the installed packages I installed Delphi XE6 Enterprise and TeeChart Pro 2014. I migrated the Delphi XE and TeeChart Pro 2010 code and recompiled. This was succesful for application not using TeeChart. Applications with TeeChart did not recompile. The bug is at TChartPen, which appears to be an unknown type although TeCanvas is in the uses clause and compilation has always been succesful with Delphi XE and TeeChart 2010. I tried several things with the unit scope names but without any success. With another third party component (dOPC) I had no problems at all. See the attachment for details.