I understand you're trying to perform column-based filtering on the series your annotated timeline will display. This is not directly supported by the 'controls' API (which was initially designed for row-based filtering) but there are workarounds for this.
Have a look at this thread where I discussed the same issue: https://groups.google.com/d/topic/google-visualization-api/fhwUv_QKfWA/discussionand proposed a working example. Also consider that the 'controls' API at the moment works fully client-side (you have to load the entire table and the controls take care of selecting the right views based on user input ). We are currently collecting usage feedback while the api is still marked as 'experimental' , so if you have a specific scenario, feel free to describe it (as said, we're already aware that column filtering would be nice to have). -- R. On 23 September 2011 17:29, asgallant <[email protected]> wrote: > The frequency of querying also comes into play. If users are going to end > up viewing most, if not all, of the columns in a single session, then query > once and be done with it. > > -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-visualization-api/-/RW5HHfEIl8EJ. > > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-visualization-api?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
