hello Daniel,
thank you for help, vaxis is the way.
P.S. I was using this graph for some time and it looked good for some
values (for example 200 in the last column) without
Vaxis https://jsfiddle.net/wnzyvftn/3/ but few days ago the value has
increased and the graph did not start at zero. I was writing it by some
example, so my mistke. Thanks again.
Dne pátek 20. října 2017 14:36:28 UTC+2 Daniel LaLiberte napsal(a):
>
> Hi Michal,
>
> You are actually using the current version, which is still 45.2.
>
> It is not clear what you mean by a problem with the last column. I would
> think all columns have the same problem. Perhaps you want to include 0 in
> your chart, which you can do by adding a minValue option.
>
> 'vAxis': { 'minValue': 0 }
>
> See: https://jsfiddle.net/wnzyvftn/3/
>
> On Fri, Oct 20, 2017 at 5:48 AM, Michal Patera <netlo...@gmail.com
> <javascript:>> wrote:
>
>> Hello I have some problem with last column in the bar graph, it should be
>> bigger thn it actually is. Could you please check it?
>> https://jsfiddle.net/wnzyvftn/
>>
>> Dne úterý 29. srpna 2017 20:46:42 UTC+2 Daniel LaLiberte napsal(a):
>>>
>>> You can now load Google Charts version '46' by loading 'upcoming'.
>>> Please test this version and let us know if you experience any new
>>> problems.
>>>
>>>
>>> At this time, 'current' is still '45.2'. You can continue to load
>>> version '45.2' by specifying that version.
>>>
>>> Anticipated production release date: Sept 19
>>> On this date, loading 'current' or 'upcoming' will load '46'.
>>>
>>> This version includes a few bug fixes, but primarily, there are many
>>> changes to the gridlines and tick generation for corecharts.
>>>
>>>
>>> Summary of changes for v46:
>>>
>>>
>>>
>>> - Corecharts
>>> - All gridline and tick generation now computes the number of
>>> gridlines based on other options (see below). If you specify a
>>> number for
>>> gridlines.count, it will only be used as an approximation.
>>> - Minor gridlines are even more dynamic since the appropriate
>>> number of minor gridlines depends on the interval between the major
>>> gridlines. The default for numeric axes is no minor gridlines, but
>>> for
>>> dates and times, minor gridlines may be shown if they fit. Specify '{
>>> minorGridlines:
>>> { count: 0 }}' to force no minor gridlines, or '{ minorGridlines:
>>> { count: 1 }}' to enable minor gridlines if they fit.
>>> - New 'gridlines.minSpacing' option lets you specify the minimum
>>> screen space between major gridlines in pixels. Default is 40 for
>>> linear
>>> scales, 15 for log scales.
>>> - New 'gridlines.interval' option lets you specify an array of
>>> sizes of the gridlines as data values. The default for linear scales
>>> is {
>>> interval: [1, 2, 2.5, 5] } means the gridline values can fall on
>>> every unit (1), on even units (2), or on multiples of 2.5 or 5. Any
>>> power
>>> of 10 of these values are also considered. For log scales, the
>>> default is [1,
>>> 2, 5]. This option is only for numeric axes at this time, and it
>>> is analogous to the 'gridlines.units.<unit>.interval' options
>>> which is used only for dates and times.
>>> - Currently, the minor gridline minimum spacing and intervals are
>>> determined automatically. These will probably be customizable in the
>>> future.
>>> - Gridlines will usually be rejected if formatted tick labels for
>>> numbers are duplicated, so you can specify 'format:"#"' to only
>>> show integer ticks without risking generation of duplicate ticks.
>>> But if
>>> all alternatives fail, the best case will still be used.
>>> - New 'viewWindow.maxMargin' lets you specify the maximum screen
>>> space before or after the data range, in percentage of the data range
>>> (as a
>>> string, e.g. '50%') or number of pixels. The default is 30%. Note
>>> that
>>> the data might extend beyond the first or last gridline occasionally,
>>> if it
>>> is not too much.
>>> - The timeofday formatting is fixed to use 24 hour (HH) values
>>> for the hours by default instead of 12 hour (hh) values.
>>> - Many changes to the log scale and mirror log scale are included
>>> in this release.
>>> - Fix for explorer mode which was disabled after the first redraw.
>>>
>>>
>>> --
>>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>> dlali...@google.com 5CC, Cambridge 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 google-visualization-api+unsubscr...@googlegroups.com
>> <javascript:>.
>> To post to this group, send email to google-visua...@googlegroups.com
>> <javascript:>.
>> Visit this group at
>> https://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-visualization-api/a0e680c9-14bc-4b65-a4d8-e33484841955%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/google-visualization-api/a0e680c9-14bc-4b65-a4d8-e33484841955%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
> dlali...@google.com <javascript:> 5CC, Cambridge 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 google-visualization-api+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-visualization-api/ab6b34d1-294d-4b06-b3f9-e223cfd610a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
