Closed GoogleCodeExporter closed 8 years ago
Original comment by socon...@gmail.com
on 28 Jun 2008 at 1:21
Pasting Jabber comment from Ray:
http://code.google.com/p/gwt-chronoscope/issues/detail?id=41
"the LegendAxis.getHeight() routine is the source of the problem of overflowing
into
the chart. I'm not sure why, it delegates to renderer.getLegendLabelBounds()
which is
supposed to compute a bounding box of all of the legend labels, + 20 pixels for
good
measure.
there are order-of-operations stuff to consider, when this getHeight() method is
called, has plot.getInnerPlotBounds() already been properly computed (the width
property accounts for axis on left and right?)
1:39 I could see a situation where getHeight() called before the width of the
plot is
available would assume that more labels could fit than really could, so
getLegendLabelBounds() would return something smaller than if called later"
Original comment by chadtaka...@gmail.com
on 30 Jun 2008 at 8:43
Resolved in r182 (see check-in comments for details); logic in
getLegendLabelBounds()
for determining bounding box for legend axis was inconsistent with logic for
positioning the labels in drawLegend(). Tested with varying number of datasets
as
well as varying dataset name lengths. See attached image for "before and after"
screen shot.
Will open up another issue (if one doesn't already exist) to address the issue
where
the legend labels "skip around" due to the numerical range values that
intermittently
get appended to the legend labels in correspondence to the user's hovering
activities
(e.g. "My Dataset" vs. "My Dataset (1.2345)").
Original comment by chadtaka...@gmail.com
on 1 Jul 2008 at 6:27
Attachments:
Original issue reported on code.google.com by
socon...@gmail.com
on 28 Jun 2008 at 1:18