Well then I'm stumped. I don't see any reason why two otherwise identical charts would draw with different size chart areas if the only difference is the range of the data. I haven't been able to replicate that effect with any other chart.
What do you do with chart1.data? Do you pass that directly to the chart, or do you use it to create a DataTable? For reference, you should create a DataTable to drive your charts instead of passing data arrays. On Saturday, May 17, 2014 4:00:37 AM UTC-4, Neil Camara wrote: > > If you look at the one of the codes that I posted earlier, I have a > setting of height: 400 > > On Friday, May 16, 2014 5:55:10 PM UTC-5, Andrew Gallant wrote: >> >> I suspect the reason the height was changing is because you never defined >> the height of the chart. Try setting either the "height" option for the >> chart (it takes a number for the height in pixels, eg "height: 400") or in >> the style/CSS of the container div. >> >> On Friday, May 16, 2014 6:11:34 PM UTC-4, Neil Camara wrote: >>> >>> Here is a sample json - >>> https://gist.github.com/c0debreaker/3c8e64722fdac6505439 >>> >>> By the way, I wrote it in AngularJS. >>> >>> - This is how I call the function >>> ----------------- >>> $scope.bigstackedchart = >>> plotStackedColumnChartTemplateForGoogleCharts($scope.jsonData, 'Total Bytes >>> Used Aggregated by World (Received/Sent)', 'user_name', 'totalbytesent', >>> 'totalbytesreceived' , 'totalbytes'); >>> >>> - and on the template, this is what is being targeted. >>> ---------------- >>> <div><div google-chart chart="bigstackedchart"></div></div> >>> >>> By the way, it's been running great right after I added viewWindow. I've >>> never seen anymore issue. >>> >>> Thanks! >>> >>> >>> On Friday, May 16, 2014 2:18:32 PM UTC-5, Andrew Gallant wrote: >>>> >>>> What is the context that you call >>>> plotStackedColumnChartTemplateForGoogleCharts in? What do you do with >>>> the returned value? Can you provide an example of jsonData passed to the >>>> function? >>>> >>>> On Friday, May 16, 2014 3:27:58 AM UTC-4, Neil Camara wrote: >>>>> >>>>> Here is the code which contains the fix on line 71. I actually just >>>>> added viewWindow : { min : 0 , max : 6000000 }, >>>>> >>>>> https://gist.github.com/c0debreaker/390245014dabf4e965d7 >>>>> >>>>> On Thursday, May 15, 2014 5:50:16 PM UTC-5, Andrew Gallant wrote: >>>>>> >>>>>> That may have fixed it, but I would consider that a temporary >>>>>> solution at best. If you could share code that replicates the issue, >>>>>> I'll >>>>>> look into it to see if I can figure out what is going on to cause it in >>>>>> the >>>>>> first place. >>>>>> >>>>>> On Thursday, May 15, 2014 4:24:07 PM UTC-4, Neil Camara wrote: >>>>>>> >>>>>>> Awesome! It's fixed! I set both min and max. >>>>>>> >>>>>>> Thank you so much! :) >>>>>>> >>>>>> -- 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 http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/d/optout.
