As of Oct 1, v46 is now 'current', and 'upcoming' will continue to load v46
until we start the next release cycle.

If you are experiencing new problems with v46, please post in the
google-visualization-api group, or on the issues list at
https://github.com/google/google-visualization-issues/issues .
Alternatively, you can switch to using the previous release by changing
'current' to '45.2', which will remain available indefinitely.



On Mon, Sep 17, 2018 at 10:31 AM Daniel LaLiberte <[email protected]>
wrote:

> I've updated the 'upcoming' v46 release again.   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*: Oct 1
>   On this date, loading 'current' or 'upcoming' will load '46'.
>
> In addition to the changes previously announced in
> https://groups.google.com/d/msg/google-visualization-api/yREgaC4x0oU/eHoBqHUNCQAJ,
> several more changes have been made, mostly fixes to previous changes.  The
> following list merges all the changes here, and highlights the new changes.
>
>
>    - 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, 20 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.
>    - Add options for gridlines.multiple and minorGridlines.multiple, such
>    that gridline and ticks values must be a multiple of this option's value.
>    E.g. To force ticks to be integers, specify gridlines.multiple = 1.
>    - 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.maxPadding' 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.
>    - Many changes to the log scale and mirror log scale are included in
>    this release.
>    - Several changes were made to the axis tick and gridline generation
>    to allow tighter packing of ticks that don't overlap.
>       - Allow negative slanted angle, to slant the 'other' way.
>       - Disable skipping and alternating (i.e. multiple staggered lines)
>       for dates and times, by default.
>    - Expand viewWindow to include explicit ticks, if outside the data
>    range.  Explicit viewWindow min or max options can override.  This is a
>    change to the previous behavior which acted more like 'maximized' mode with
>    explicit ticks.
>    - Fix for explorer mode, which was disabled after the first redraw.
>    - Fixed ChartWrapper refreshInterval to actually refresh.
>    - Trendline equations now use column labels instead of just 'x' and
>    'y'.
>    - Fix polynomial trendlines to fail silently if there is no data.
>    - Add option to specify legend default page index (legend.pageIndex).
>    - Add event (legendpagination) to receive updates of legend pagination
>    changes; data given to event handler is         'currentPageIndex' and
>    'totalPages'.
>    - *Number format for 'short' and 'long' patterns now use 3 significant
>    digits.*
>    - The timeofday formatting is fixed to use 24 hour (HH) values for the
>    hours by default instead of 12 hour (hh) values.
>    - *Explicit formats for dates and times will now override 'unit'
>    formats.*
>
>
>    - Histogram chart
>       - Domain axis gridlines and baseline default color is 'none'.
>       - Target axis ticks default format is now '#', to display integers
>       only.
>       - *Generate buckets using tick generation algorithm.*
>       - *Default number of buckets is computed using a new
>       histogram.numBucketsRule option.  Possible values are 'sqrt', 'sturges' 
> and
>       'rice'.
>       See https://en.wikipedia.org/wiki/Histogram#Number_of_bins_and_width
>       <https://en.wikipedia.org/wiki/Histogram#Number_of_bins_and_width>*
>
>
>    - ColumnChart and BarChart
>       - Fixed detection of minimum bar size (the difference between
>       adjacent values) to work with dates and times.
>
>
>    - Table
>       - Support 'className' property for rows.
>       - Add user specified column and cell className properties to
>       default properties (rather than replace them), similar to row
>       properties.
>
>
>    - Data
>       - Fix the data.group function to allow multiple aggregations to use
>       the same column.
>
>
>    - *Content Security Policy (CSP) compliance*
>       - *Remove uses of eval for JSON deserialization.*
>
>
> --
> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
> [email protected] <[email protected]>   Cambridge MA
>


-- 
Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
[email protected] <[email protected]>   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 [email protected].
To post to this group, send email to [email protected].
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/CAOtcSJNQBbYseq1U6%2BunTGOL6ZO5A6YQAvizzL3XuANxLNMSLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to