Google Charts 45.1 in 'upcoming'

1,183 views
Skip to first unread message

Daniel LaLiberte

unread,
Dec 5, 2016, 4:36:14 PM12/5/16
to Google Visualization API
I have updated Google Charts for 'upcoming' to load v45.1, which contains mostly refactoring changes for security, and a couple small bug fixes:  
  • corecharts: Fix to avoid failures when chartArea bottom and right options are too large.
  • Gantt chart: Now returns 'row' property in selected items.
Please test and report problems here.

After a week of testing, the 'current' version, which is now v45, will redirect to v45.1, and 'upcoming' will again be the same as 'current'.  And if problems show up then, I can quickly switch back to v45.  

This is a new way of deploying the release that should avoid caching problems as we have experienced in the past.  

--

Benjamin Hill

unread,
Dec 5, 2016, 7:28:54 PM12/5/16
to Google Visualization API
Gantt chart fix you just made my day.  Thank you!

Khrys

unread,
Dec 27, 2016, 12:05:54 PM12/27/16
to Google Visualization API
I notice the custom font for Gantt isn't working anymore. I have it set for other charts like line, area and timeline working.

Khrys

unread,
Dec 27, 2016, 12:07:24 PM12/27/16
to Google Visualization API
BTW, can we get what changed? Thanks. : )

Mahaz Nisar

unread,
Dec 30, 2016, 9:23:02 PM12/30/16
to Google Visualization API

Daniel LaLiberte

unread,
Dec 31, 2016, 1:53:28 PM12/31/16
to Google Visualization API
Hi Mahaz,

Nothing has changed on the 'upcoming' version for a couple weeks, so a change that occurred just in the last day is not likely to be related to the 'upcoming' version.  I was waiting for some more feedback on possible issues before releasing it, but it sounds like what you have encountered may be related to caching.  I will try your code to see what happens for me though.  

Does it work for you if you specify '45'?  If so, that narrows down where the problem might be.

--
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+unsub...@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/cc41aff0-a3a0-4523-a01e-68a31796e5ce%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Daniel LaLiberte

unread,
Dec 31, 2016, 2:00:02 PM12/31/16
to Google Visualization API
Mahaz,

Your code appears to work fine for me here:  https://jsfiddle.net/dlaliberte/vmjewh93/

There are a couple differences in the html and body tags, but otherwise, it should behave the same for you.  Do you see an error in this example?

On Sat, Dec 31, 2016 at 1:53 PM, Daniel LaLiberte <dlali...@google.com> wrote:
Hi Mahaz,

Nothing has changed on the 'upcoming' version for a couple weeks, so a change that occurred just in the last day is not likely to be related to the 'upcoming' version.  I was waiting for some more feedback on possible issues before releasing it, but it sounds like what you have encountered may be related to caching.  I will try your code to see what happens for me though.  

Does it work for you if you specify '45'?  If so, that narrows down where the problem might be.
On Fri, Dec 30, 2016 at 9:23 PM, Mahaz Nisar <abbasi....@gmail.com> wrote:
Dear Daniel,
please help to solve my problem.
https://groups.google.com/forum/?hl=en#!topic/google-visualization-api/54mLRq_YI60 

On Tuesday, December 6, 2016 at 2:36:14 AM UTC+5, Daniel LaLiberte wrote:
I have updated Google Charts for 'upcoming' to load v45.1, which contains mostly refactoring changes for security, and a couple small bug fixes:  
  • corecharts: Fix to avoid failures when chartArea bottom and right options are too large.
  • Gantt chart: Now returns 'row' property in selected items.
Please test and report problems here.

After a week of testing, the 'current' version, which is now v45, will redirect to v45.1, and 'upcoming' will again be the same as 'current'.  And if problems show up then, I can quickly switch back to v45.  

This is a new way of deploying the release that should avoid caching problems as we have experienced in the past.  

--

--
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.
--

Daniel LaLiberte

unread,
Jan 4, 2017, 11:11:12 AM1/4/17
to Google Visualization API
Google Charts 45.1 is now 'current', and the same as 'upcoming'.

I delayed this stage of the deployment (switching 'current' to be the same as 'upcoming') until now, partly because of some additional issues and questions about whether it was working correctly, but also because of the holidays.  

If 'current' is causing problems for you, please report here, but in the meantime, you can load '45' instead, if you want to stick with that version.

Sugihara Shinya

unread,
Jan 4, 2017, 7:50:45 PM1/4/17
to google-visua...@googlegroups.com, Endo Yosuke, Nakamura Takahide
各位

Googke Chartのバージョンがアップデートされました。
NXのライングラフはバージョン固定されており、
直近で更新する必要はありません。

以上、よろしくお願いします。

-----------------------------------------------------------------
株式会社ネオレックス  http://www.neorex.co.jp/
杉原 進哉
TEL:052-681-2121

On 2017/01/05 1:11, 'Daniel LaLiberte' via Google Visualization API wrote:
> Google Charts 45.1 is now 'current', and the same as 'upcoming'.
>
> I delayed this stage of the deployment (switching 'current' to be the
> same as 'upcoming') until now, partly because of some additional issues
> and questions about whether it was working correctly, but also because
> of the holidays.
>
> If 'current' is causing problems for you, please report here, but in the
> meantime, you can load '45' instead, if you want to stick with that version.
>
> On Monday, December 5, 2016 at 4:36:14 PM UTC-5, Daniel LaLiberte wrote:
>
> I have updated Google Charts for 'upcoming' to load v45.1, which
> contains mostly refactoring changes for security, and a couple small
> bug fixes:
>
> * corecharts: Fix to avoid failures when chartArea bottom and
> right options are too large.
> * Gantt chart: Now returns 'row' property in selected items.
>
> Please test and report problems here.
>
> After a week of testing, the 'current' version, which is now v45,
> will redirect to v45.1, and 'upcoming' will again be the same as
> 'current'. And if problems show up then, I can quickly switch back
> to v45.
>
> This is a new way of deploying the release that should avoid caching
> problems as we have experienced in the past.
>
> --
> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
> dlali...@Google.com <mailto: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-visualizati...@googlegroups.com
> <mailto:google-visualizati...@googlegroups.com>.
> To post to this group, send email to
> google-visua...@googlegroups.com
> <mailto:google-visua...@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/86c870d5-6848-412c-96d1-73191aa80f7b%40googlegroups.com
> <https://groups.google.com/d/msgid/google-visualization-api/86c870d5-6848-412c-96d1-73191aa80f7b%40googlegroups.com?utm_medium=email&utm_source=footer>.

Facundo Ferrer

unread,
Jan 16, 2017, 3:21:55 AM1/16/17
to Google Visualization API
Hello Daniel,

I've realized that my code stop working after the change of 'current' version to v45.1. I do some checks inside of a DataTable structure and it seems that some keys has changed.
This is the example code that stop working for me:
let dt = google.visualization.arrayToDataTable(da);
if (data.Sf[0].type == 'datetime') { ....

Now I had to change it to:
if (data.pg[0].type == 'datetime') { ....

Maybe this is not the correct way to check the data type of one of my columns but in any case if the version is updated (to 45.1 in this case) I would expect a new release in the official release page otherwise is weird that 'current' version is not pointing to Septmber 12, 2016 release.

Best regards,

Daniel LaLiberte

unread,
Jan 16, 2017, 9:29:29 AM1/16/17
to Google Visualization API
Hi Facundo,

You should definitely not use the obfuscated properties inside the data or chart objects, since they will change, even with the very same version occasionally, if need be.  There is a getColumnType() method that you could have used for what you wanted.   https://developers.google.com/chart/interactive/docs/reference#DataTable_getColumnType

Version 45.1 is almost the same as 45, at least from the API perspective.  The changes were mostly internal refactoring and a couple small bug fixes, so I decided to treat this as just an update of the last release.  I haven't updated the documentation yet to include the bug fixes.

Lerne uns auf Facebook und LinkedIn kennen.

Geschäftsführer: Benjamin Hermann, 
Dr. Stefan Zerbe. Amtsgericht Stuttgart HRB 22526, Gerichtsstand Stuttgart. Die genannten Angaben werden automatisch hinzugefügt und lassen keine Rückschlüsse auf den Rechtscharakter der E-Mail zu. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.

--
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+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Facundo Ferrer

unread,
Jan 16, 2017, 10:58:53 AM1/16/17
to Google Visualization API
Hi Daniel,

it makes totally sense. I will update my code. 

Thanks,
To post to this group, send email to google-visua...@googlegroups.com.



--

Ravi Sawney

unread,
Jan 27, 2017, 11:05:14 AM1/27/17
to Google Visualization API
Would be great to know where to look for a reference on such settings as chartArea bottom - cannot seem to find anything on the popular search engine...

sachin pawar

unread,
Apr 25, 2017, 6:47:58 PM4/25/17
to Google Visualization API

dsf
Reply all
Reply to author
Forward
0 new messages