Page 1 of 1

Various Polar/PolarBar Series problems

Posted: Fri Oct 06, 2006 12:08 pm
by 9642212
Hi,

There are some problems when using a Polar or PolarBar Series.

1.
Most of Zooming seems not to work. I can't get region zooming to work and zooming a rectangle shows problems.

To Zoom In, I use the following code (inserted in a MouseEventHandler and attached to MouseClick event of the chart):

Code: Select all

... // some code which I left out, since not relevant

Rectangle chartRect = tChart.Chart.ChartRect;
int newZoomWidth = chartRect.Width * 2/3;
int newZoomHeight = chartRect.Height * 2/3;
Rectangle zoomRect = new Rectangle(e.X - newZoomWidth/2, e.Y - newZoomHeight/2, newZoomWidth, newZoomHeight);
tChart.Zoom.ZoomRect(zoomRect);

... // some code which I left out, since not relevant
So basically a rectangle around the clicked point is zoomed in. This works perfectly when using a Line Series (or sth. else), but when using a Polar or PolarBar Series, the result is that the chart zooms out by a certain factor.

2.
The CursorTool doesn't work as expected.

- It gets stuck in a certain quadrant (the 4th). If depends on the plot it is associated with, more in detail to which axes this plot is attached.
The first image shows the default behavior, the 2nd if I changed the Series' associated Left Axis to Right:

ImageImage

- If you enable it to snap to a certian plot, it snaps to various locations in that quadrant, but none seem relevant.

You can easily replicate these problems by adding a TChart to a form. Add a Polar Series to it, a CursorTool (associate it with that Series). Then play a little with the Series' associated axes and the CursorTool Settings and you'll see the behaviors I explained.


3.
If I try to invert all the axes (bottom, top, left, right), some do, some don't. It only works for the Left Horizontal and Top Vertical axes, as can be seen in the following screenshot:

Image

Also the plot doesn't make sense anymore.

Conclusion:

I think that all these problems are originating from the fact that the polar graph is "misusing" the normal axes in a polar chart (always got the impression that it is squeezed into a concept that isn't made for it).

The bottom axis is used for the right horizontal axis, the left axis for the bottom vertical axis. A normal plot is attached to the bottom and left axis, so as a result this would only cover the 4th quadrant, which could explain why the cursor gets stuck there and why it changes if you change the associated axes of the Series.

Also inverting the axes, only makes sense if you invert them all (since they share the same scaling = radius of circle). In my code I make sure that all the axes share the same settings, but this doesn't seem to work for the Inverted Property.

Also, I thought it had something to with the fact that you can set the associated axes of a Series to Both, which I don't do normally. But changing this doesn't seem to have any effect.

Regards

Posted: Mon Oct 09, 2006 11:34 am
by narcis
Hi dimitrig,

Please. find below the answers to your questions:

1. This is because polar series doesn't support zooming. This is already an item in our wish-list to be implemented for future versions.
2 and 3. Those are bugs which I've added to our defect list to be fixed for future releases. Their IDs are TF02011813 and TF02011815 respectively.

Posted: Mon Oct 09, 2006 1:42 pm
by 9642212
Hi NarcĂ­s,

1. Do you have any idea when this item will be added? I've noticed that it isn't supported for the Smith Series either, which is even more important to us.
If you could just give me an idea what the priority / estimated time is, I can evaluate what I'm going to do with it. Maybe I'll have to try, to implement some workaround for it myself, if it's going to take too long (e.g. > 1 year).

2 and 3. Ok... thanks.

Posted: Tue Oct 10, 2006 8:54 am
by narcis
Hi dimitrig,

No, we still don't have any date for this being implemented. I guess that won't be implemented in TeeChart for .NET v2 since we are currently working on v3. We expect to release TeeChart for .NET v3 before the end of the year. So if this feature was implemented it would be in v3.