Hiding items on a plot using BoxAndWhiskerRenderer

[mminer]

I have a CategoryPlot rendered by a BoxAndWhiskerRenderer. On this plot I have a DefaultBoxAndWhiskerCategoryDataset, which contains twelve items. I would like to temporarily hide a row on this dataset, or even the whole thing. However, I'm unable to do so. I would expect the following code to hide something, but it seems to have no effect (the zero can be substituted for any number).

Code: Select all

CategoryPlot plot = (CategoryPlot)getPlot();
Boolean visible = new Boolean(false);
plot.getRenderer().setSeriesVisible(0, visible);

Any ideas? Is it simply not possible to hide items rendered by a BoxAndWhiskerRenderer?

[Priya Shivapura]

Looks like this is a bug in the BoxAndWhiskerRenderer. The visibility is not being checked when the items are being drawn. For now, you could extend the BoxAndWhiskerRenderer, override the drawHorizontalItem and drawVerticalItem and add the following two lines in the beginning

Code: Select all

// do nothing if item is not visible
if (!getItemVisible(row, column)) {
         return;   
}

Regards,
Priya

[RichardWest]

Looks like this is a bug in the BoxAndWhiskerRenderer.

I would not necessarily say this is a bug. When the setSeriesVisibility() method was added, not all renderers implemented it. The reason being is that some renderers rely on information from all the series to render correctly, and the visibilty complicates the logic. The body fir this method has been written on a per demand/per available-time basis.

[mminer]

For now, you could extend the BoxAndWhiskerRenderer, override the drawHorizontalItem and drawVerticalItem and add the following two lines in the beginning

Thanks Priya, that worked like a charm.

Though it may not be a bug, it certainly seems like it is when the setSeriesVisibility() does nothing despite being given the proper index of the series. The API documentation for CategoryItemRenderer gives no hint that the method may not work in some of its subclasses.

[Paul Belleville]

I used this work around, and it works great.
I am using 1.0.9. Does anyone know if it is implemented in the newest version such that I don't need the work-around?

[david.gilbert]

No it's not. I'm adding it now for the 1.0.12 release.