Jonathan, It appears you discovered that the minValue and maxValue options only expand the range of values in the chart, and as such, they are not as useful as they could be. They also don't determine the bounds of the axis directly, but only determine what the chart thinks are the min and max values of data.
The axis bounds are actually determined by several things including what values of ticks (also used for gridlines) seem to fit best for the data. Since the numbers 41 to 49 are not as good for the tick values, it jumps from 40 up to 50. You'll see similar things as you add more rows. What you want is really the 'viewWindow' min and max options, which do determine the bounds of the axis. You can set the viewWindowMode to 'explicit', or leave it undefined to get the default behavior. Another issue is likely to be with your gridlines, since regardless of the size of the viewWindow, the tick values will still gravitate to nice round numbers. If you always want 4 subdivisions across all your values, no matter what the values are, then you will probably want to specify explicit tick values with the new 'ticks' option. Give it an array of values that you calculate yourself. In your case, you'll subdivide the range of numbers 0 to n by 4. For example, if you have 44 values, use ticks: [0, 11, 22, 33, 44]. Hope that helps. On Sun, Aug 18, 2013 at 9:30 AM, Jonathan Roy <[email protected]> wrote: > In further testing, since I use -1 direction and 0 is the right far of the > chart, it's the max value that causes an issue not the minimum value. > > If I leave maxValue out, it scales properly up to 40 rows. At this point > it then wants to jump the chart to 50 max horizontal value instead of the > actual highest value, even if I specify maxValue. If I put a maxValue much > too high I get great scaling effect (of course), if I set it too low it's > ignored. > > So looking at the auto scaling related options I tried viewWindowMode: > 'maximized' which fixed the issue, other than the outer border of the chart > disappearing on the left side. > > It wasn't intuitive to me that not specifying any viewWindowMode would > default to a setting that would override my maxValue to provide more pretty > steps in the interior lines. But I guess this is pretty much the answer. > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to > [email protected]. > Visit this group at > http://groups.google.com/group/google-visualization-api. > For more options, visit https://groups.google.com/groups/opt_out. > -- Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> - 978-394-1058 [email protected] <[email protected]> 562D 5CC, Cambridge MA [email protected] <[email protected]> 9 Juniper Ridge Road, Acton MA -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/groups/opt_out.
