I tried an example now and it seems ok.Do you want to send me an example where you observed this slowness.
On Wed, Jul 15, 2009 at 7:41 PM, [email protected] < [email protected]> wrote: > > The data is already aggregated into year-long bits. It really is not > very much data, so I'm not sure what's going on. > > Thanks for the tip though. > > On Jul 12, 9:52 am, ChartMan <[email protected]> wrote: > > I don't know of any issue but the chart does "work harder" when trails > are > > on. If you are using a lot of data you can try using a smaller input by > > aggregating the data over weeks/months etc. > > Let me know if this solution works for you. > > > > ChartMan > > > > On Fri, Jul 10, 2009 at 10:12 PM, ramen <[email protected]> wrote: > > > > > Hi. I have implemented motionChart, and it works fine and everything > > > moves around great, but whenever I turn trails on, my computer > > > practically freezes. I am not using terribly much data (20kb total of > > > CSV). Do you think that the trails are just not designed for tracing > > > out lots of data? Is there anything I can do to fix the lagging? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
