frankCA

Hi All, My company has purchased fusioncharts v3 and we're going to implement zoom line chart in our product, which will replace a bunch of widgets we had already coded (date slide, time field, period combo with aggregation and dynamic interval support etc... etc...) The zoom line chart looks tres cool, especially the effect of zooming nicely from a macroscopic view down to real raw data. However there is one problem which has been deemed unacceptable by product management. "If the chart is in macroscopic view, many data points are skipped in order to accommodate the entire series of data." This approach potentially (and usually) wipes peaks, skipping a datapoint can remove a potentially important peak. For example, given a macroscopic view of financial data, stock prices, for a year. at 11am on the 3rd of january, stock price spiked to $100 where usually it's $30. In macroscopic view you wouldn't see this spike, instead you'd see a nice stable consistant line. Not Good. Question to the forum, am I missing something, has anyone had this same problem/requirement with zoom chart, and if so how did they achieve their goal??? thanks in advance... Frank.

Hi, I'm in need of sycnhronising scrolling of charts. That is, display contains 4 scrollable fusioncharts, user scrolls one chart and the other 3 charts also scroll. I notice that over the last couple of years other customers have asked the same thing, see threads below... Is there plans on including something like this ? http://forum.fusionc...-scroll-charts/ http://forum.fusionc...nction-exposed/ Thanking you, Frank Fera

sorry that should read - I code the above zoomto after rendering (trapped via FC_Rendered/rendered event) to control the macroview to display the default zoom I'm after intead of the default macroview which skips datapoints. Still not ideal, typically if you're selling the fact that you have a chart package with the very cool ability to display a macroview with subsequent zooming. The macroview should be an accurate representation showing peaks etc... correctly. For example, if you have one years’ worth of hourly data that you want to fit on a chart without skipping datapoints. Support a "type" attribute, and then perform relevant aggregation on the datapoints to enable the data to be shown in larger intervals, to enable less datapoints, and therefore no skipping on the chart. Based on the type specified, aggregation would be done to provide the relevant value which aggregates 24 hourly datapoints into ONE DAILY datapoint. For example, there could be a type supported that would represent 24 hourly datapoints of [1,0,0,0,3,4,5,6,9,1,1,4,6,8,6,20,0,0,0,0,0,0,11,1] into one DAILY datapoint of 20 (the highest value for that period). Another aggregation type could be one DAILY datapoint showing the SUM of all those values. The chart would be fed the rawest data (in the above case hourly interval datapoints) and the charting code would perform the relevant aggregation to change the interval based on how many datapoints can fit on the chart. I think this is basic charting principles (unless I'm grossly out of line here). Thoughts? Thanking you, Frank Fera

Hi, thanks for your response, but that doesn't address the macroview issue .... UNLESS, by above you suggest the following... On initial view (so user hasnt done anything yet) to stop the macroview from skipping datapoints, I code the above in zoomto after rendering (via FC_Rendered/rendered event) to control the macroview as I wish. Is this what you mean ?