TeeChart2012 and TDraw3D bug for CB6

[anauta2013]

I found new issue that exists in the Chart under CB6
The constuction like:

TCanvas3D *c = Draw3D1->Canvas;
c->Pen->Width = 3;
will produce Access Violation.
I had to return to TeeChart2011 to avoid this bug.

[vlezhu]

Hi, Yeray.
And what do you think about this bug?

[Yeray]

Hi,

I've created a new simple project in BCB6 with just a Chart on the form, a TLineSeries created and populated at design time, and the code above (Chart1 instead of Draw3D1, since the chart is named Chart1 by default) at FormCreate, and I see no error at all.

Could you please arrange a simple example project we can run as-is to reproduce he problem here?

Thanks in advance.

[vlezhu]

Sorry for poor information in the first post, I thought that it is clear.
This is example without chart, only TDraw3D component was used.
Will put TDraw3D to form and then place

TCanvas3D *c = Draw3D1->Canvas;
c->Pen->Width = 3;

to the constructor of the form1.

After start of application you will see this error in CB6.

[Yeray]

Hi,

Sorry for poor information in the first post, I thought that it is clear.
This is example without chart, only TDraw3D component was used.

Sorry, my bad.

I've tried it with just a TDraw3D added on the form at design time and the code you mention in the FormCreate, and the application compiles and runs without problems for me here with TeeChart v2012.06 and C++Builder 6, in a Win7 64bit machine.

Are you reproducing this with v2012.06?

[anauta2013]

Yes, I can reproduce it on TeeChart2012 V.6
By the way, I work on Win7-32, may be this is reason?
I upload test project Test.zip

[Yeray]

Hi,

I can open your project without any error. I found it gave me an error when trying to find Tee9C6.lib. I've closed the project and edited the .bpr manually to remove the all the references to Tee9C6. I've reopened the project and it builds and runs fine for me here.
It makes me think it has to be something in the paths on your IDE.

[anauta2013]

I could not find the reason for this behaviour, but after total reinstall of CB6 the bug dissappeared, thank you for the tip.