smerchek

Members
  • Content count

    11
  • Joined

  • Last visited

About smerchek

  • Rank
    Junior Member
  1. Problem serverside image saving - latest rev 3.1

    The problem I am seeing is not on the server side. I can recreate the issue by just using the sample code (C:sourceFusionCharts_EnterpriseCodeExportChartSamplesServerSideSelectedFormats.html) without calling a valid server side script. I have captured the post using live http and have created an image.txt file with the parameters from the post. I have seperated the start of where the colors are incorrect. I have attached the sample files I am using and the client side post data ============================================ System: Windows XP Prof SP3 Browser: Firefox 3.0.9 ============================================ Chart: Column3D.swf Height: 300 Width: 400 SelectedFormats.html.txt SelectedFormats.xml image.txt
  2. Problem serverside image saving - latest rev 3.1

    Any progress on this?
  3. Corrupt Rendering in FusionChart V3.1

    Check out the documentation here: http://www.fusioncharts.com/docs/Contents/Debug/Window.html
  4. Problem serverside image saving - latest rev 3.1

    The python code was the first place I looked and dumped the stream variable and saw that the colors were incorrect in the raw data. After that I used live http to capture the actual post from the flash object and saw the same incorrect colors. I have attached the live http image, python code and also the post parameters. post.txt python.txt
  5. I have implemented a Python side image download. This is working well, thanks to schmichael. The problem that I am having is with the actual post from the chart swf. The color values passed are not correct for all of the chart. I am using the provided SelectedFormats example. I have attached the original and the exported image. XML: chart yAxisName='Sales Figure' caption='Top 5 Sales Person' numberPrefix='$' useRoundEdges='1' bgColor='FFFFFF,FFFFFF' showBorder='0' exportEnabled='1' exportAtClient='0' exportAction='download' exportHandler='http://test.server/fcexporter/saveImage/' exportFileName='MyFileName' >
  6. seriesNameInToolTip broken in 3.1

    I emailed support as well. I did receive a response and a new swf the chart I was having a problem with, but I'm sure that there are multiple charts with this problem. I have requested more info on was the issue was and what charts are affected.
  7. seriesNameInToolTip broken in 3.1

    I am also having the same problem with the StackedColumn3D chart. The seriesname is now missing.
  8. This was a great post. ( fix our cpu problems ) I ran into cpu usage issues many months back when trying to use the wmod=transparent. Our dashboard had issues in both IE and FF. We are running an internal dashboard under FF2, we have probably 40 browser windows open with 60-65 flash objects. We pretty much eat up most of the dual core, we run two instances of FF and both processes consistently use 35 - 50 %. We tried FF3 with just 1 browser window and 5 flash objects and it immediately hits 50% cpu. Today I set the framerate to 5, since we are not doing any animation, and our dashboard now averages about 10-20% cpu usage.
  9. I can update the dial value. I don't know if this is just the way it works or not. I would like to use the datastream option to update the dial, trendpoints and annotations in realtime, instead of having to use the setdataurl, since it redraws the entire gauge. Anyone know how to get this to work or is it a not yet implemented function??? Thanks.
  10. I am also trying to accomplish the same types of things, but with the angular gauge. I am using extjs to create windows and place a gauge within it. I need the transparent option to allow moving the windows around to keep z-order in check. I can open 6 gauges with no hit on the cpu, but when the 7th gauge is created then the cpu consistently jumps to around 22-25% then when the 8th gauge is created the cpu is around 50% and stability becomes a problem. I have tested with both firefox and IE and firefox only has the issue. Still doing more testing.