[visualization-api] Grouping data after filtering

Hello I'd like to have a dashboard which filters some raw data, then prepares the data for a chart (by grouping rows). For example, say I have a table with sales transactions (date, store, category, amount). I'd like to allow the user to filter by category and then show a chart of

[visualization-api] Re: Motion Chart Background Color

Did you ever find an answer to this? On Tuesday, February 23, 2016 at 5:22:52 PM UTC-8, Logan Meltabarger wrote: > > I have not found a recent answer to thishas the ability to change the > motion chart's white background to a different color been enabled? > > If not, is there a method to

Re: [visualization-api] category tooltips and selection show wrong category when column chart is scrolled

Hi Suzanne, Posting questions about an issue in the forum first is a good idea. When you are sure you have found a bug, then posting on the GitHub issues list is fine. For your issue, this is a known problem area, which should be better documented at least. If your chart container element is

[visualization-api] category tooltips and selection show wrong category when column chart is scrolled

This is a bug report (btw, am I better off reporting this here in the forum, or on the github site, or does it not make a difference?). I have a column chart inside a div with overflow:auto. Thus, when the specified width exceeds the width of the div, the chart is scrollable. So far so

Re: [visualization-api] ChartWrapper with nonzero RefreshInterval creates new queries when the .draw() method is called

It doesn't appear to be difficult to fix, and it is a rather serious problem when it occurs, akin to an infinite loop. So I would expect to address it relatively soon. On Thu, Oct 27, 2016 at 11:41 AM, Chad Hanna wrote: > Hi Daniel, > > Thanks for confirming this. I

Re: [visualization-api] ChartWrapper with nonzero RefreshInterval creates new queries when the .draw() method is called

Hi Daniel, Thanks for confirming this. I thought I might need to rework things to use lower level classes. It would be wonderful if this could be fixed in ChartWrapper since I plan to make a lot of charts and ChartWrapper is otherwise entirely adequate and makes for simpler code. Is there any