DannyR

Can you post your code please?

Not sure. Can you post a code snip? Also, pretty sure that call into Ext won't work (but I could be wrong).

Please post your solution.

To be fair, the HTML5 fallback does seem a little rushed, but I can understand their desire to get that functionality into their users' hands as quickly as possible. Yes, it does not have near the level of polish we've come to appreciate at the Flash end of the product, but it most cases so far I've found it to be more than satisfactory. Being a hardcore UI guy, I'm doing everything in Javascript (I don't use XML at all). I've written a class that instantiates the chart object, and then sub-classed it to create the different type of graphs I want. That way, as these guys continue to bugfix their fallback implementation, I can just change everything in one place without having to actually rewrite any of my graphs. So a typical implementation for me would look something like this: <div id="myChart"></div> <script language="JavaScript"> var jsonData = { chart: { yaxisminvalue: "0", yaxismaxvalue: "100", numDivLines: "3" }, data:[{ value: "30" }] }; FusionCharts.setCurrentRenderer("javascript"); var chart = new FusionCharts("../../js/FusionCharts/Column3D.swf", "myChart-chartId", 300, 200); chart.setJSONData(jsonData); if (!!chart._overrideJSChartConfiguration) { chart._overrideJSChartConfiguration({ yAxis: [{ tickInterval: 25 }] }); } chart.render("myChart"); </script> So, the chart is constructed as normal, but in this particular case, I've used _overrideJSChartConfiguration() to fix a defect where the fallback is not respecting the numDivLines property of the chart object. So when this gets fixed in a later release, I can just delete the override (or leave it there for that matter). All this can be done in one "page" as you say. Hope that answers your question.

Chris - Here's the method I use: var chart = new FusionCharts(..); // only true if js chart if (!!chart._overrideJSChartConfiguration) { // } Hope this helps.

The short answer is because there are two completely different rendering engines depending on whether the chart is flash or HTML5. They are working on translating all the formatting of one type to the other, but it is definitely what I'd call a "work in progress". The good news is that most (if not all) of the imperfections can be rectified by using an override method exposed in the JS API. If you can attach your data source I can try and take a quick look at this one to see about correcting the x-axis labels. The two different graphs are NEVER going to be exactly alike - nor should anyone expect them to be. There is a massive canyon between Flash and SVG.

You could try leveraging Dojo's i18n implementation, depending on what your needs are.

Little known secret (I found out last week because I debugged the source), FusionCharts implementation of HC ALWAYS uses 2 Y axes. So at the very least, your solution would have to as well. Since you're only using one on your bar chart, you can simply encapsulate your object in an array: Instead of: yAxis: { labels: { align: "left", rotation: 0, }, tickmarkPlacement: "on" } Use: yAxis: [{ labels: { align: "left", rotation: 0, }, tickmarkPlacement: "on" }] Let me know if that gets you closer to your solution, and if not, gimme some code snips and I'll debug it for ya.

Hi David - It does look to me that the fallback for the labelDisplay, rotateLabels, slantLabels attributes of <chart/> are not working correctly in fallback mode. I'd have to do some more testing to be sure exactly under what conditions its failing (and file a bug), but first I wanted to give you a hand. The good news is that we can hook the HTML5 version of the chart and override. Add this code before the render - it should work for ya: if (!!myChart._overrideJSChartConfiguration) { myChart._overrideJSChartConfiguration({ xAxis: { labels: { align: "center", rotation: 0 } } }); } Let me know how you make out. =]

David - If you post a code snip, I'll take a look at it and get back to you shortly.

Mork = work ;] Let us know how you make out.

labelStep might mork for you. Take a look in the doc for spline here: http://www.fusioncha...tSS/Spline.html

Are you running the code on a web server or are you trying to do it from the filesystem? Have you tried using getChartFromID and checking in Firebug to see what methods are exposed?

Ah, I understand what you're asking now. Had to read it a few times. Widgets is a whole different kettle of fish. There is a limited JavaScript API that you can read about here. The methods exposed by FusionCharts.js don't apply.

Np!

David, there is a JavaScript API to allow you to control the export any way you want. Take a look at the doc here.

The JS file is also part of the evaluation install. If you downloaded your trial version before yesterday, just get the new one.

Can you please post your XML or JSON data source?

Need to see some code. Also, what version(s) of IE are you looking at?

This is really frustrating me. I need to have a chart whose Y-Axis is in the range of 0-100. The SWF version works as expected, however the HighCharts version does not. I tried overriding using _overrideJSChartConfiguration, however it respects NOTHING on the yAxis. See below: <script language="JavaScript"> var jsonData = { chart: { caption: "Title", yaxisminvalue: "0", yaxismaxvalue:"100" }, data:[{ label: "Name", value: "30" }] }; FusionCharts.setCurrentRenderer("javascript"); var chart = new FusionCharts("../../js/FusionCharts/Column3D.swf", "myChart-chartId", 400, 300); chart.setJSONData(jsonData); if (!!chart._overrideJSChartConfiguration) { chart._overrideJSChartConfiguration({ chart: { borderRadius: 15 // works }, credits: { enabled: true, text: "CREDITS works" }, yAxis: { max: 100, gridLineColor: "#FF0000", title: { text: "YAXIS does not" } }, xAxis: { title: { text: "XAXIS works" } } }); } chart.render("myChart"); </script> We're coming up on a VERY important release, so I need to get this resolved ASAP!

As reported here: http://forum.fusionc...-y-axis-limits/ Looking at the source code, your implementation of HighCharts plotOptions object ALWAYS uses 2 Y-Axes, as seen below: plotOptions: { yAxis: [{ startOnTick: false, endOnTick: false, title: { style: {}, text: '' }, labels: { style: {}, formatter: function () { return parseStr(v(this.value, a.chart, 1)) } }, plotBands: [], plotLines: [] }, { gridLineWidth: 0, startOnTick: false, endOnTick: false, title: { style: {}, text: '' }, labels: { style: {}, enabled: false, formatter: function () { return parseStr(v(this.value, a.chart, 2)) } }, opposite: true }] } Since your code actually merges in the end-user's overrides (which I like), it was necessary to frame the yAxis property of the object argument to _overrideJSChartConfiguration() like so (note that yAxis property is now an array of objects): if (!!chart._overrideJSChartConfiguration) { chart._overrideJSChartConfiguration({ yAxis: [{ title: { text: "YAXIS label override works!" } }] }); } Voilà! Hope this can help someone besides me!

Excellent! Email sent, awaiting your reply. You'll be happy to know that this problem is INDEED fixed with the Evaluation version - I'm very pleased! Just waiting on the "real" version now. Many thanks!

How do I get an updated licensed version and not the eval version?

That's because all block <div>s by default are 100%. 2 ways to approach the problem. The outdated way is to make a 3-column table. The "modern" way is to use something like this: <div id="left" style="width:200px; float:left; border:1px solid black;">LEFT</div> <div id="right" style="width:200px; float:right; border:1px solid red;">RIGHT</div> <div id="middle" style="border:1px solid blue;">MIDDLE</div> Season to taste. ;]

Since you're using Firebug, put a watch on your inner variable "chart". You'll see all the methods that are exposed.