Stacked data's tooltip is unintuitively ordered

[Sam Halliday]

Dear all,

I have an AreaChart with stacked data.

When the 'focusTarget' is set to 'category' then all entries in a row
are shown in the tooltip. However, they are the wrong way round with
respect to the data and this is very confusing for a user.

For an example of this effect, have a look here http://jsfiddle.net/FAXQ8/2/

Is there any way to

1. have this fixed on the Google side

or

2. work around this, with a minimum of fuss?

Regards, Sam

[Sam Halliday]

(I should note that setting "vAxis.direction: -1" doesn't solve the
problem because it turns the whole vertical axis upside down which
isn't what I want)

On Dec 27, 7:24 pm, Sam Halliday <sam.halli...@gmail.com> wrote:
> Dear all,
>
> I have an AreaChart with stacked data.
>
> When the 'focusTarget' is set to 'category' then all entries in a row
> are shown in the tooltip. However, they are the wrong way round with
> respect to the data and this is very confusing for a user.
>

> For an example of this effect, have a look herehttp://jsfiddle.net/FAXQ8/2/

[Jinji]

Indeed, a bug. Should be fixed in the next version.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.

[Sam Halliday]

Talking of versions - is it possible to request a specific version of the Google Visualization API? (I am delivering some code to a customer which uses GViz and I don't want to have to be called in for support if something subtle)

[asgallant]

*sigh* Join the waitlist.  The only versions you can specify are the current release (1.0) or the current RC (1.1).

[Sam Halliday]

ok, excellent, so I specify version "1.1" and there won't be any major changes to the API forever?

[Jinji]

On the contrary. See http://code.google.com/apis/chart/interactive/docs/library_loading_enhancements.html#loadthevisualizations

On Wed, Dec 28, 2011 at 4:55 PM, Sam Halliday <sam.ha...@gmail.com> wrote:

ok, excellent, so I specify version "1.1" and there won't be any major changes to the API forever?

--
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/-/_Xyu5Ccgr9oJ.

[Sam Halliday]

Eek!!! That's horrible and against the conventions of other Google APIs http://code.google.com/apis/loader/ whereby stable releases are denoted by version numbers (MAJOR.MINOR.BUGFIX) and wildcards specify development releases (e.g. MAJOR.x). The exception seems to be that "1" is often used to mean "the absolute latest".

What guarantees can you provide that a future 'stable' version (i.e. "1.0") of the API will not break my application deliverable?

In order to mitigate the risk of unforeseen compatibility issues, there needs to be release "versions" and a policy of forwards compatibility within those versions. Breaks in forwards compatibility should imply a new version number. If this were the case, then "1.0" would mean "the latest stable release of version 1" and "1.1" (or "1.x" in keeping with conventions) would mean "the latest experimental release of version 1)" and breaks in compatibility would imply releasing "2.0"/"2.x", "3.0"/"3.x" etc. You could of course, optionally, release specific versions such as "1.0.1" for use by the exceptionally paranoid.

[asgallant]

Like I said, join the waitlist.  This has been on my wishlist pretty much since Day 1 (almost a year ago now!).

There are no guarantees that your code won't break - in fact, it may be the opposite for some users.  As an example, there is a version coming out soon that will make a major change to the way axes with 'numeric' types are handled.  If you built code that exploited the "undocumented feature" that allowed for numeric-typed axes in some charts (previously not officially supported), then your charts will break when this release is pushed unless you fix them.  To their credit, the Charts team gave plenty of notice, but I still expect there will be users flooding these forums with "why did my charts break" questions when that release is pushed.