I've updated v46 (aka 'upcoming') with the following changes, in addition
to the previously announced changes:
- Corecharts
- Rename viewWindow.maxMargin to viewWindow.maxPadding.
- Fix defaults for Histogram domain axis gridlines and baselineColor, and
targetAxis should display integers with format: '#'
- 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.
- Change 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 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'.
- Table
- 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 fix multiple aggregations using the
same column.
Please try this version out and post any new problems you encounter,
particularly with the axis ticks and gridlines. If this appears to be
stable I will try again in a couple weeks to push it to 'current'.
On Fri, Jan 12, 2018 at 10:21 AM, Sean Larson <industrepren...@gmail.com>
wrote:
> Ajinkya, your option123 is not configured correctly. Try:
>
> var options = {
> title: 'My Big Chart',
> width: 400,
> height: 300,
> legend: { position: 'left' }
> }
>
> I am not sure which charts support 3d, look in the reference documents,
> https://developers.google.com/chart/interactive/docs/gallery/barchart
>
>
>
>
> On Wednesday, November 22, 2017 at 11:36:55 PM UTC-6, Ajinkya Loke wrote:
>>
>> I have started using Googlecharts for my sharepoint site and using
>> javascript I am trying to display charts.
>> I am current not able to customize it if I want to change the colors of
>> the bars or even legend on the left. I am not able to do that inspite of
>> providing it in the options parameter.
>> Not sure abt the issue. Can anyone guide. Default color scheme and legend
>> on right is displayed well. but no customization works
>> Here is my code.
>>
>> <script src="https://www.gstatic.com/charts/loader.js";
>> type="text/javascript"></script>
>> <script type="text/javascript">
>> google.charts.load('current', {'packages':['bar','line']});
>> google.charts.setOnLoadCallback(visualizeData);
>> function visualizeData() {
>> var data1 = new google.visualization.DataTable();
>> data1.addColumn('string', 'Weekly Status');
>> data1.addColumn('number', 'AL 2');
>> data1.addColumn('number', 'AL 3');
>> data1.addColumn('number', 'AL 4');
>> data1.addColumn('number', 'AL 5');
>> for (var i=SummALDate.length-1; i>=0; i--)
>> {
>> var row1 = [];
>> row1.push(SummALDate[i]);
>> row1.push(SummAL2[i]);
>> row1.push(SummAL3[i]);
>> row1.push(SummAL4[i]);
>> row1.push(SummAL5[i]);
>> data1.addRow(row1);
>> }
>>
>>
>> var options123 = {
>> legend:'left',
>> title:'My Big Chart',
>> 'is3D':true,
>> 'width':400,
>> 'height':300
>> }
>> var barChart = new google.charts.Bar(document.get
>> ElementById('BarChart'));
>>
>> barChart.draw(data1, options123);
>> </script>
>>
>>
>> On Wednesday, August 30, 2017 at 12:16:42 AM UTC+5:30, Daniel LaLiberte
>> wrote:
>>
>>> 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.
> 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/3d558a91-de42-4a63-b092-
> edf19aa1f2ff%40googlegroups.com
> <https://groups.google.com/d/msgid/google-visualization-api/3d558a91-de42-4a63-b092-edf19aa1f2ff%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>
dlalibe...@google.com <dlalibe...@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.
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/CAOtcSJMndioLP5eC-6JCFyNVBryMfMgQuN2YBEN1tC6Ev9Xe%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
