Steema Central

Hello,

For several years I used a trick to reduce cpu usage when redrawing a CursorTool.
Recently I upgraded to TeeChart 2011.03.30407 (Delphi 2007) and discovered a problem with MDI forms. The attached program demonstrates the problem.
When using default drawing, everything is working fine but cpu usage is very high.

Now set the drawing type to fast and open 2 or more MDI children. Move one of the MDI forms over another one and away and see that the cursortools isn't being updated any more. The only way to correct that is resisizing the MDI form.

What do I have to do to correct this problem? I have the sources.

Regards,
Bert

Hello Bert B.

Could you tell us in which version your Trick works as you expected?

Thanks,

This trick was verified to work with versions 7.12 and 8.06.

Hello Bert,

I could reproduce the problem from v2010.00 so I've added it to the wish list to be investigated for future releases (TV52015541).
However I see we recommended you to use custom drawing also for performance reasons here. Doesn't it work fine for you?

Hello Yeray,

The recommended custom drawing isn't working for me for the following 3 reasons.

1) Stability. Try the 3 different methods. Suddenly your recommended method isn't working anymore. The cursor can only be seen in the upper part of the chart.

2) The mouse cursor keeps flashing if it is over the chart. That is caused by the constant redraws of the chart.

3) Code simplicity. With you method I have to override every ChartAfterDraw and declare a variable IsBuffering.
My method can be put in a simple procedure where you have to supply the CursorTool and the desired Value.

It is not fair to say 'my method', because you are using it yourself in the examples. See procedure CursorSynchronize in Tool_CursorSynchro.pas.

Regards,
Bert

Hi Bert,

Thanks for your feedback. I have updated and incremented issue's priority in the defect list.

Hello,

It has been 4 months since I reported this issue and I still haven't got a fix.
When will this be fixed?
I don't need the useless Twitter/Facebook/... answer.
As a comparison: when I report a bug to Developer Express, the fix is usually there within a dew days. What a difference!

Regards,
Bert

Hello Bert,

We have been doing some tests with this issue and we think it is fixed with our current sources. I'll send you an email with the sources we think are working fine for us. Can you please check if they solved the problem at your end? If that's the case you could expect it to be fixed in next maintenance release.

Thanks in advance.

Hello Narcís,

It seems that the bug has been fixed. Good work!

Regards,
Bert