clemens.s

Hi there! Sry that I kept you waiting - I was on a short vacation I've tried your suggestion and it _kinda_ works. The charts itself is rendered again, but it is much faster (and the loading-bar is gone). I'm going to get the XMLData once per Ajax, store it and get it the next time faster (after switching tabs). Thanks again for your time and patience. Greetings, Clemens

Hi, i've tried it out, and this would solve the 'rerendering' problem. Unfortunately there seems to be a limitation (acording to your documentation @ FusionCharts_Enterprise_3.1.1/Contents/DataXML.html) of the length a DataXML can have: Since I expect (and i know there will be) a an large amount of data, the DataXML-Method seems to be not the best solution for me. I've played around with setting the DataXML per javascript, but i think this is just not possible (or is it?). Thanks for your time. Greetings, Clemens

Hi, thanks for the answer and clearing it up. I'm not sure if i understand your question (english issn't my first language) - i use the "dataURL" method to get the XML into the chart (which is served by a PHP script). Is there any way to work around this problem? Greetings, Clemens

Hi, first of all: neat work! - keep it up. Now my issue: We are using the charts for reporting in a tabbed interface. Basicly it looks like this: < div id="tab1" onclick="switchTab(this)" > < div id="chartdiv_1" >Here goes the first Chart< /div > < /div > < div id="tab2" onclick="switchTab(this)" > < div id="chartdiv_2" >Here goes the second Chart< /div > < /div > To switch between the tabs, we change the display-attribute of the different tabs (e.g.: if we want to see tab1, we will display:block on tab1 and display:none on tab2). So when look at the chart on tab1, switch to tab2 (look at the chart there), and switch to tab1 back, the chart is displaying a "loading ..." message, and rendering the chart again. That would be ok - if the data wouldn't been pushed from the server again. If seen this behaviour in the following browsers: Firefox 3.5, Opera, Safari and Chrome. Only in IE6 and IE7 it worked like I would expect it (one of those scary "omg it works in IE but in all other browsers not"-moments). Is there any way to get rid of this behavior? Greetings, Clemens