CursorTool not working properly - endless slow - 100% CPU

TeeChart for Microsoft Visual Studio .NET, Xamarin Studio (Android, iOS & Forms) & Monodevelop.
Post Reply
Elric
Newbie
Newbie
Posts: 2
Joined: Fri Nov 15, 2002 12:00 am
Contact:

CursorTool not working properly - endless slow - 100% CPU

Post by Elric » Tue Sep 26, 2006 11:12 am

We want to move a CrossCursor across the Chart. This supports the user to easily see the intersection points on the axes.
We have 1 to n (up to 20) series drawn on the Chart.
Using the Cursortool CPU usage goes up to 100%. Additionally the Cross is not following the mouse immediately. It is always behind the arrow which indicates the cursor movement.

The code we use to activate the cursor:

TChart1.Tools.Add(cursor1)
cursor1.FollowMouse = True
cursor1.Style = Steema.TeeChart.Tools.CursorToolStyles.Both

We posted this problem over a year ago but the problem is still there in the newest version we downloaded.

As the CrossCursor is a Customer request the solution of the problem is very urgent for us.
Can you make a statement about intended bugfixes to this problem, or do you know a workaround ?

Thanx in advance

Marjan
Site Admin
Site Admin
Posts: 745
Joined: Fri Nov 07, 2003 5:00 am
Location: Slovenia
Contact:

Post by Marjan » Tue Sep 26, 2006 1:01 pm

Hi.

What's the total number of points per series ? I'm guessing here but most likely the number of points is large (compared to number of pixels i.e. chart size). Does the same problem occur when you reduce the number of points in series ?
Marjan Slatinek,
http://www.steema.com

Elric
Newbie
Newbie
Posts: 2
Joined: Fri Nov 15, 2002 12:00 am
Contact:

Post by Elric » Tue Sep 26, 2006 3:07 pm

Hi,
You are right, the more points are loaded the slower the cursor reacts. But i can't see the context (perhaps you can explain)
The CPU usage is always near 100% regardless the number of points per series.
The size of the the Chart is controlled by our users. The proposal to decrease the number of points per series will not be a solution to our problem.

Post Reply