Face Chart Zoom

[Chris82]

1. Smart GWT EE Showcase
http://www.smartclient.com/smartgwtee/showcase/#cityPopulationZoom
http://www.smartclient.com/smartgwtee/showcase/#stockPricesZoom

2. Chrome 30.0.1599.69 m, Firefox 24.0

When using the zoom chart examples I've found that the horizontal scroll bar used to move the bottom chart is not working as I would expect.

-As you move it left and right the scroll bar does not stay in the same relative position as the vertical bars.
-When the scroll bar hits the left or right arrow or the section vertical bars hit either end the section between the two vertical bars begins to decrease, rather than just stopping
-The left and right arrows do not move the scroll bar

Hope this helps. We would like to start using zoomable charts, but these issues are holding us back right now.

Thanks,
Chris

[Isomorphic]

These are intended behaviors, which closely follow the very popular Yahoo Finance charts and other similar zoomable charts.

[Chris82]

That is not entirely true. I just tried the Yahoo finance chart. The scroll bar stays in the middle of the 2 vertical bars when moving around. It does not change its position relative to the 2 bars.

It also has no arrows on the horizontal scroll bar whereas facet charts have them. If they are there then they should do something (like the google finance charts)

The only thing Yahoo! finance does that I pointed to below is point #2.

I also tested with Google Finance Chart and works differently as well.

-Chris

https://www.google.com/finance?q=INDEXDJX%3A.DJI&ei=40NcUsiyEYislAOX_QE

http://finance.yahoo.com/echarts?s=%5EDJI+Interactive#symbol=%5Edji;range=1d;compare=;indicator=volume;charttype=area;crosshair=on;ohlcvalues=0;logscale=off;source=undefined;

[Isomorphic]

We agree on #3 - something should happen if you click the arrows. We'll fix this.

On #1, between our implementation and Yahoo's, there's a tradeoff between tracking the position of the bars vs the slightly weird effect that moving that moving the mouse while the thumb is stationary resizes the range, and the track doesn't reflect the actual range of meaningfully distinct positions of the bars. Then Google's behavior is entirely different (and we would say the worst of the bunch). We don't see a clearly best behavior here.

[Isomorphic]

We've corrected #3 for tomorrow's 4.0 and 4.1 builds. Clicking in the track area was also not quite right, and we fixed that too.