I just pasted the code directly into a new project created with the flex 3.5 sdk, it ran fine, I then updated the project to 4.0 sdk and it ran fine, I then disabled spark in the build options and once again it ran fine.
This is on windows 7 x64, so FB seems to being handling the charting demo with no issues at all.
Well That's very odd, because if I run it after compiling it with Flex 3.5 or 4.1 as mentioned without ver 3 compatibility turned on it does work.
The problem I have is that I'd like to compile to more easily port over with the flag set on. Again I get no error during compile but when I run it I get
the error described. So apparently the code is broken somewhere during the porting and I'd hate to rewrite my complete application over in Flex 4.
Going forward I can see writing to the spec, but it should be backwards compatible?
1 person found this helpful
for me backward compatibility is a no-no, to much drama with support, I hate legacy code and for me the moment FB 4 went public I labelled everything flex 3 legacy and started the porting.
I have the same problem with my application. I have found a workaround. The problem is that for an unknown reason the "itemRenderer" property of PieSeries is null. To solve this problem you can specify the itemRenderer property to its orignal default value.
Something like :
I hope it will help.
De Saint Florent
Ouch...the Data Visualization package contains all kinds of fun surprises like this. You'd think Adobe would want to fix the many remaining bugs since it's a very marketable feature, but they seem to have lost interest in it. At least now it's open source, which helps a lot in sorting things out. Of course it exposes a new kind of pain from trying to figure it all out. They never bothered to clean up before going open, so the design still wreaks of being closed off (only now you can better plan workarounds). Customizing the DV components is way more difficult than it has to be.