Re: [flexcoders] Re: AreaChart bug when changing 'type' property

2008-02-19 Thread Guido
Has anyone had this problem? I mean, that when changing the 'type' property for an AreaChart only the first series (first meaning, the only one declared in MXML, whereas secondary would mean ones added on AS). My mxml code was posted earlier on this thread, but I'm posting a new version,

Re: [flexcoders] Re: AreaChart bug when changing 'type' property

2008-02-19 Thread Guido
Sorry, forgot to mention that I realize it might be a difference that in the mxml code some properties ar bound because of the curly braces, and that doesn't happen when assigning the property in AS. But still, the objects assigned to these properties do not change overtime, and that's why I don't

Re: [flexcoders] Re: AreaChart bug when changing 'type' property

2008-02-14 Thread Guido
Hi, and thank you guys for answering. I've tried removing the interpolation effect, and it doesn't blow up anymore, although it still doesn't work properly. When changing the AreaChart's type, only the series defined in mxml (i.e. as in the sample code I sent) gets either stacked or 100%'ed.

[flexcoders] Re: AreaChart bug when changing 'type' property

2008-02-13 Thread jer_ela
I had the same thing. I believe it is due to the interpolate effect not liking stacked or 100% charts. When you change the type, the effect runs and that is what is blowing up. I had this problem with both area and column charts. I added code to remove the effect before changing to a stack or