Box plot automatic scales problem

[Michal Blazejczyk]

Hi,

I have just discovered an annoying bug. My application displays several box plots using UseCustomValues=true. Here's sample code:

Code: Select all

            box1.Clear();
            box1.UseCustomValues = true;
            box1.Add( new double[] {9.1, 9.4, 10.1} );  // outliers only
            
            box1.Median = 5.0;
            box1.Quartile1 = 2.4;
            box1.Quartile3 = 6.1;
            box1.InnerFence1 = 2.1;
            box1.InnerFence3 = 6.8;
            box1.OuterFence1 = 1.5;
            box1.OuterFence3 = 7.5;
            box1.AdjacentPoint1 = 1.0;
            box1.AdjacentPoint3 = 8.0;

Problem: The automatic scaling doesn't take into account the box location, only the outliers! This means that if the outliers lie only on one side of the box, the box will not be visible - it will be outside of the default axis range.

I have just spent a few hours hunting this one down

Best,
Michal Blazejczyk

[Narcís]

Hi Michal,

Thanks for reporting.

I could reproduce the issue here and added it (TF02011538) to our defect list to be fixed for future releases.

[Marjan]

Yes, the problem is I forgot to override the MaxYValue and MinYValue methods (for box, for horizontalbox the MaxXValue and MinYValue) in case custom values are used. I've just fixed this ... the fix will be included in next maintenance release.

[eda2013]

Dear sir,

This issue still not been fixed for new release.
Do you have a workaround until you fix this bug?

[Narcís]

Hi eda2013,

The issue was fixed back in August 2006. I have checked it works fine for me here using latest TeeChart for .NET release, build 4.1.2013.07300. Which TeeChart version are you using?

[eda2013]

Hi, Narcis

We use TeeChartNET2013_4.1.2013.07300 with Visual Studio 2008 and the UseCustomValues is false.
The raw data is below,but this box chart is wrong.
You can see the value of median or AdjacentPoint in box.

Index Samples
0 93.53
1 99.02
2 99.409
3 89.953
4 99.44
5 95.93

[Narcís]

Hi eda2013,

Ok, thanks for the info. I have added the defect to the bug list (TF02016719) to be fixed for future releases.