Hi, So as mentioned in this thread, there is no implementation for re-query-ing that is part of the library.
If anyone has a general use implementation, we will have to add a link from our tools gallery ( http://code.google.com/apis/visualization/documentation/toolsgallery.html) Regards, VizGuy On Thu, Sep 3, 2009 at 2:08 PM, Bob <[email protected]> wrote: > > Zach, > What I've got is a need, and the realization that all the things > I've tried have failed for me. They can be made to work in a fashion, > but I need production code, and these are just not doing it. > So I've held off and made it something the user has to ask for in > the GUI. > There's also the annoying "white out" when redrawing an ATL with a > lot of data, but that I've solved by a simple double-buffering scheme > of having two ATLs at the same location in the page and drawing to the > "background" one and then flipping them with the CSS zIndex property. > That works very nicely and it gives me nearly instant updating of > the data. > However, I can't say that I've cracked the other. > Sorry. > > Bob > > > On Sep 2, 2:04 pm, Zach Dwiel <[email protected]> wrote: > > Bob: do you have any clean working code to use as an example? > > > > I've been working on a similar hack, which relies on hideDataColumns > > and showDataColumns columns (using a column for each level of zoom). > > However, sometimes, the range gets messed up. This seems to happen > > because it gets to a state between switching columns where there are > > no columns displayed instead of despite a specific order of operations > > in the code. > > > > Do you have something that works? > > > > I'd be happy to share some of my code if anyone is interested in > > trying to get it straightened out. It works for the most part. > > > > thanks > > > > zach > > > > On Sep 2, 8:32 am, Bob <[email protected]> wrote: > > > > > > > > > Volt, > > > You might not like the answer, but in general, what you're going to > > > need to do is to re-query for the higher (or lower) resolution data > > > when you zoom. > > > You can get intercept the zoom events by adding a listener for the > > > 'rangechange' event and then seeing what the old and new limits of the > > > range are. Based on those limits, you'd re-query your source and > > > redraw that AnnotatedTimeLine for that new data set. > > > Of course, when you needed to zoom out, you'd need to do the same, > > > but this time, getting the *lower* resolution data. > > > It's not ideal, but that's as good as you can currently do with the > > > AnnotatedTimeLine. > > > I, too, wish there were a more feature-rich data buffering scheme > > > with the ATL... but at current, there just isn't. > > > > > Bob > > > > > On Sep 1, 12:46 pm, Voit <[email protected]> wrote: > > > > > > Does anybody have information I need - how to make Annotatedtimeline > > > > to show/hide values on zoom ? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
