I see. That's a pity. I'm back to having issues with misaligned gridlines, then. Just tried manually setting ticks and the problem remains the same.
Anyway, thanks for your help Daniel, I hope we can see those changes in a near future! On Tuesday, 4 August 2015 15:37:58 UTC-3, Daniel LaLiberte wrote: > > My mistake. The isStacked option doesn't apply to individual series, > since you have to stack a group of series. We are thinking of adding a way > to specify which series go in a group, hence my confusion. > > So this bug with the line chart axis in a combo chart with stacked bars is > not so easy to work around after all. The only workaround is to manually > set the viewWindow min for your line chart axis to be what you intend. > > On Tue, Aug 4, 2015 at 2:25 PM, Moustacheful <[email protected] > <javascript:>> wrote: > >> No problem! and thanks again for the quick reply! >> Then I believe I might have found another bug, since setting the column >> series to 'isStacked' does indeed fix the axis scaling but no longer stacks >> the columns, unless I'm doing something wrong. >> >> You can see the issue here: >> http://jsfiddle.net/c9k2xz1d/2/ >> >> >> >> On Tuesday, 4 August 2015 14:29:23 UTC-3, Daniel LaLiberte wrote: >>> >>> Looks like you did find a bug, but it is easy to work around and not >>> very likely to cause problems for most people. The bug is caused by your >>> top-level isStacked: true option, which should not affect line charts, but >>> since you have columns elsewhere in the chart, it does affect the line >>> chart by adding the baseline (= 0) to the axis. To work around this, you >>> can remove the top-level isStacked option and only add it to the series >>> with the columns (bars). >>> >>> Thanks for reporting this, and going to the trouble of reproducing it. >>> >>> On Tue, Aug 4, 2015 at 11:59 AM, Moustacheful <[email protected]> >>> wrote: >>> >>>> Sorry, apparently I did not save the last fiddle, here goes: >>>> http://jsfiddle.net/c9k2xz1d/1/ >>>> >>>> >>>> On Tuesday, 4 August 2015 12:54:02 UTC-3, Moustacheful wrote: >>>>> >>>>> Thanks for your reply. I see about the gridlines. I'll try defining >>>>> the ticks and see if it works. >>>>> >>>>> About the behaviour I'm seeing: >>>>> >>>>> here you can see the second axis (percentage) on its own >>>>> https://jsfiddle.net/udet1vwb/2/ >>>>> >>>>> If we add a new axis the result is the following >>>>> https://jsfiddle.net/c9k2xz1d/ >>>>> >>>>> as you can see, the second vertical axis seems flattened, considering >>>>> it does not have any points where the data is below 70%. >>>>> >>>>> I'll give baselines a try now. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tuesday, 4 August 2015 11:07:59 UTC-3, Daniel LaLiberte wrote: >>>>>> >>>>>> Setting the gridlines count to a fixed number for both left and right >>>>>> axes doesn't mean the gridlines will line up because gridlines don't >>>>>> necessarily land at the top and bottom of the chart. This is true even >>>>>> if >>>>>> you specify the viewWindow min and max, though the viewWindow bounds >>>>>> will >>>>>> be respected. The gridlines that are computed by the heuristics may >>>>>> determine that slightly better ticks result if it doesn't put a gridline >>>>>> at >>>>>> either extreme, or at both extremes. >>>>>> >>>>>> We don't yet have a way of specifying the gridlines using an interval >>>>>> between gridlines together with a baseline value. That would provide a >>>>>> fairly straightforward solution, but until then, you should probably >>>>>> just >>>>>> use the explicit 'ticks' option, together with the viewWindow min and >>>>>> max. >>>>>> >>>>>> Regarding the 'flattening' of the chart, this is probably due to the >>>>>> baseline value of 0 being added to the chart, once the heuristics see >>>>>> that >>>>>> it is "close enough" to the rest of your data. I don't believe that >>>>>> just >>>>>> adding a second axis would cause that, since the axes are computed >>>>>> independently, so I expect you forgot about another change you had made. >>>>>> If >>>>>> you can provide a link to a page demonstrating what you saw, we can take >>>>>> a >>>>>> look. >>>>>> >>>>>> Hope that helps. >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Aug 3, 2015 at 5:21 PM, Moustacheful <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hello. I've been working for a while on a project and I noticed >>>>>>> something weird. >>>>>>> >>>>>>> Whenever I have a *single axis chart* (for example for percentages) >>>>>>> >>>>>>> >>>>>>> https://drive.google.com/file/d/0B-SPOI3uVlh2a3ExOUhfVlB6M1k/view?usp=sharing >>>>>>> >>>>>>> And then I add a *new axis* into the mix (numeric), the scale of >>>>>>> the first axis changes and gets 'flattened' visually. (unsure whether >>>>>>> this >>>>>>> is a bug or a feature) >>>>>>> >>>>>>> >>>>>>> https://drive.google.com/file/d/0B-SPOI3uVlh2TUoxazJzZ0tLeVE/view?usp=sharing >>>>>>> >>>>>>> I tried setting specific *viewWindow min-max* values (by >>>>>>> calculating the minimum and maximum of all the series on that axis >>>>>>> together) which while it works, results in some weird display for the >>>>>>> gridlines (which are both set to count:10, so they should be >>>>>>> automatically >>>>>>> and evenly generated) >>>>>>> >>>>>>> https://drive.google.com/open?id=0B-SPOI3uVlh2U0tFZWZyZ1VyMmc >>>>>>> >>>>>>> I either need to: >>>>>>> Solve the scaling problem and leave everything automatic or >>>>>>> Solve the gridlines problem when setting viewWindow min and max >>>>>>> values manually >>>>>>> Any ideas? >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>>>> http://groups.google.com/group/google-visualization-api. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Daniel LaLiberte >>>>>> <https://plus.google.com/100631381223468223275?prsrc=2> - >>>>>> 978-394-1058 >>>>>> [email protected] 5CC, Cambridge MA >>>>>> [email protected] 9 Juniper Ridge Road, Acton 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 >>>> http://groups.google.com/group/google-visualization-api. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> >>> - 978-394-1058 >>> [email protected] 5CC, Cambridge MA >>> [email protected] 9 Juniper Ridge Road, Acton 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] >> <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at >> http://groups.google.com/group/google-visualization-api. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> > - 978-394-1058 > [email protected] <javascript:> 5CC, Cambridge MA > [email protected] <javascript:> 9 Juniper Ridge Road, Acton 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 http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/d/optout.
