> The email suggests a quick solution to converting these values to string > using a DataView, so you won't have any sorting issues. > Please take a minute to look at the suggestions we made (using a DataView). > It's a very easy and quick change. How many charts are we talking about?
I read your suggestion about using DataViews. If it's that simple, then why don't you modify the charts to automatically do that conversion on their own? That way we wouldn't need to modify all of our code. You would make the change in a single place, allowing us to benefit from that, instead of requiring us to make that change in multiple locations. Your change would be backwards compatible. So if it's as simple as the workaround suggests, why not do that in the core chart classes? > I agree, and still, the fact is that it was never supported. See But it works. I see no reason to break it now. If you're working on a better change for the future, then keep this working now. Or implement the workaround in the charts themselves, as I suggested above. > I disagree about the "without any problems" parts. The support we intend to > add (and doesn't exist at the moment) is important to many users. And the currently working functionality you are taking away is important to many other users. Again, I implore you to not do this. You are literally destroying the faith many of us had in your products. The lack of version control is a major problem, and radical changes to the way the charts work have catastrophic effects on smaller companies that don't have the resources to continually update their chart code everytime you put out a non-backwards compatible release. -- 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.
