Hi

Indeed this behavior was changed in the last release.
We will hopefully address this in the upcoming release (which are now more
frequent than before).

Sorry for any inconvenience,
  Viz Kid

On Fri, Feb 25, 2011 at 4:22 PM, Remo <[email protected]> wrote:

> This behaviour is really bad for charts showing percentages. Check out
> the following uptime chart for example:
>
> function drawVisualization() {
>    var data = new google.visualization.DataTable();
>    data.addColumn('string', 'Datum');
>    data.addColumn('number', 'Uptime');
>    data.addRows([['25.01.2011', 91.23],
>                  ['26.01.2011', 71.23],
>                  ['27.01.2011', 100.0],
>                  ['28.01.2011', 100.0],
>                  ['29.01.2011', 81.23],
>                  ['30.01.2011', 100.0]]);
>
>  var ac = new
> google.visualization.AreaChart(document.getElementById('visualization'));
>  ac.draw(data, {
>    title : 'Uptime Chart',
>    width: 600,
>    height: 400,
>    vAxis: {title: "Uptime (%)", minValue: 0, maxValue: 100}
>  });
> }
>
> If you run this code in the playground (http://code.google.com/apis/
> ajax/playground/?type=visualization#area_chart) you will see, that the
> specified maxValue=100 is ignored even all values are <= 100 and that
> the chart uses 120 as maxValue of vAxis which makes absolutely no
> sense in case of a percentage chart.
>
> And we are using version 1, not 1.1 (where this problem also exists).
> This used to work as expected until last week or so.
>
> Cheers Remo
>
>
> On Feb 20, 12:38 pm, visigoth <[email protected]> wrote:
> > Tomas,
> >
> > Your observation is correct, and indeed the fixes to version 1.1 come
> > to solve cases like the 0, 8, 15, 23, 30 you mentioned.
> > Our algorithm prefers 0,30,60,90,120 over 0,25,50,75,100 because it
> > does not give multiples of 5 enough emphasis. We might address that in
> > a future release.
> > BTW, the first option (0-120) is actually preferable in some cases, so
> > it could be that adding user control over tick values is inevitable
> > (also to specify a rigid max value above which the range cannot be
> > extended).
> >
> > Your notes will be taken into account when we revise our tick choosing
> > mechanism.
> > Thank you,
> > visigoth
> >
> > On Feb 17, 5:24 pm, tkapler <[email protected]> wrote:
> >
> >
> >
> >
> >
> >
> >
> > > one bug (if not strange "feature") with 1.1
> >
> > > linechart - when i set vAxismaxValueto 100, it uses 120 instead. On
> > > version 1.0 it works as expected. Actually it starts to show 120 when
> > > i havemaxValueover 90.
> >
> > > The same with e.g.maxValue60 - it shows 80 (but 59 shows 60).
> >
> > > Seehttp://mediacentrum.cz/bug.htmandcompare it withhttp://
> mediacentrum.cz/not-bug.htm(theonly difference is that
> > > version 1.1 versus 1)
> >
> > > I guess that you are trying to round it on "nice" numbers (5 / 10)
> > > sooner (so e.g. with 30 it is 0, 8, 15, 23, 30 with v.1, but 0, 10,
> > > 20, 30, 40 with version 1.1), but IMHO you should accept rounding to 5
> > > for higher numbers - e.g. that 100 is very common max value for vAxis
> > > for showing percentages).
> >
> > > And of course the best would be to use always themaxValuewhen it is
> > > set and do not try to increase it - when i do not want default
> > >maxValuecalculated from data, i probably know why i do not want that
> > > default value. And if i would need some inteligence over it, i could
> > > very easily calculate from my data and put it tomaxValue. The same
> > > for minValue.
> >
> > > P.S.: when you will repair it, you can put there that grid granularity
> > > variable ;-) (i guess that there would be somewhere in the code number
> > > 5 for splitting in 5 section, so replacing it with variable with
> > > default=5 would not take long ;-)
> >
> > > Tomas
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Visualization API" group.
> To post to this group, send email to
> [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-visualization-api?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Visualization API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-visualization-api?hl=en.

Reply via email to