Wedge Stack Group breaks in example with more data added in xml :(

[GoogleCodeExporter]

What steps will reproduce the problem?
I've been pulling out my hair for many hours on this one and can't
figure out a solution for the life of me yet.  to reproduce the bug
just change the number of outer wedges in the 2008 example.
1.change the 2008 olympics xml to the following:
<country name="USA">
           <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
            <medal category="Gold" count="36"/>
           <medal category="Silver" count="36"/>
           <medal category="Bronze" count="38"/>
       </country>
        <country name="Netherlands">
           <medal category="Gold" count="7"/>
           <medal category="Silver" count="4"/>
           <medal category="Bronze" count="5"/>
       </country>
2. run the app

What is the expected output? What do you see instead?
expect to see the outer widges to render properly. 

What version of the product are you using? On what operating system?
Beta 1.0 (latest) on Mac os X 10.6

Please provide any additional information below.
 it seems that the max arc isn't binding properly to the arc of the inner wedge properly on 
runtime (not 100% sure though) .   I can only reproduce when the outer wedges 
are binded to the 
innerwedge.  also running in debug mode with different breakpoints will 
sometimes show 
different results.  from my testing it has come down to 
'maxArc="{innerWedgeGroup.wedge.arc}"' 
that what appears to not be working correctly.  

I really hope you can help :)

Thanks,

Miles

Original issue reported on code.google.com by adammile...@gmail.com on 21 Dec 2009 at 5:19

[GoogleCodeExporter]

By repeatedly calling invalidateDisplayList on the DataCanvas, the chart will 
eventually redraw correctly, but it fails just as often.

Original comment by mvand...@gmail.com on 28 Dec 2009 at 9:47

[GoogleCodeExporter]

hey mvandani,

So did you have any luck with the invalidateDisplayList as a work around? 

Thanks,

Miles

Original comment by adammile...@gmail.com on 30 Dec 2009 at 4:03

[GoogleCodeExporter]

I have an idea for a work around but it involves creating the wedgegroups 
dynamically.  But have had no luck 
adding it to the data canvas after the data canvas as already been created.  
any ideas?

Miles

Original comment by adammile...@gmail.com on 31 Dec 2009 at 8:47

[GoogleCodeExporter]

I have the same probleme, and an other one when there are only one medal 
category for
one country

Thanks,
Ludo

Original comment by ludovic....@gmail.com on 5 Jan 2010 at 4:48

[GoogleCodeExporter]

Hi guys! 
It seems that the State defined in the outerWedgeGroup messes the values up and 
more
specifically when you want to change the property "outerRadius" of the target
outerWedgeGroup.wedge. Temporary solution will be to remove from the state
outerWedgeGroup.wedge from targets array, outerRadius from properties and
outerRadius.value*1.2 from values.

Tony

Original comment by maverix7 on 25 Jan 2010 at 3:29

[GoogleCodeExporter]

Forget about the last... it's not that case at all

Tony

Original comment by maverix7 on 27 Jan 2010 at 2:55

[GoogleCodeExporter]

Original comment by maverix7 on 21 Feb 2010 at 3:00

• Changed state: Started

[GoogleCodeExporter]

Finally, the problem comes from the time the elements need to render (because of
their amount). The GeometryRepeater handles this, but errors like that occur 
when
having nested groups. I started fixing it

Original comment by maverix7 on 21 Feb 2010 at 3:10

[GoogleCodeExporter]

The issue was fixed in the development branch

Tony

Original comment by maverix7 on 22 Feb 2010 at 10:50

• Changed state: Fixed