Good timing for that question. I have the code written and will be showing it on my next blog post, in a few days. So stay tuned.

Bea

Please let us know if you have the updated version of LabeledPieChart for Nov09 release of DataVisualization Toolkit.

Regards,
-Saju

I am using a simple algorithm to place the labels – they simply get placed in the middle point of that arc. So, no, I don’t have a solution implemented that improves the scenario you describe.

It wouldn’t be that hard to extend the code in this blog post to do that though. If you decide to do so, please post the link to it here so that others can benefit from your work.

Thanks!
Bea

There is problem in implementing the labeling suppose i have three values 95% , 2.5% and 2.5% when labele is generated, for last two value they are overlapped.So there is no clear visibility. I am using LabelDisplayMode=”Connected”

Is there is any solution for this is yes please suggest.

Thanks
Anil Kumar

Hmm… not sure I understand… the labels are not in the toolkit – that is the point of this post. :)
Any charting feedback that you (and others) leave on my blog, I simply send David email with the details. You can also leave feedback to David directly on his blog.

Thanks for your comment!
Bea

Regarding Template.FindName: GetTemplateChild exists both in WPF and Silverlight, but it’s protected in both technologies, so you can only use it within the code for the derived control. The code I show here is not in the definition for the chart, it’s in some other class where chart is used. FindName in WPF searches for an element within a particular namescope. myControl.Template.FindName searches for an element within the template for the control specified.

In Silverlight 3, it’s not possible to data bind non-FrameworkElements, and GradientStop is not a FrameworkElement. So that scenario is not supported in Silverlight, whether you use Binding or TemplateBinding. It’s unfortunate that no error message is displayed.
In WPF, you can use Binding on non-FrameworkElements, but not TemplateBinding. You should get an error message if you try to use TemplateBinding in this scenario.

Bea

I don’t know WPF, so I’m not sure if it’s exactly the same, but in SL there’s a GetTemplateChild method.

// chart inherits from Control
PieChartLabelArea labelArea = chart.GetTemplateChild(“LabelArea_PART”) as PieChartLabelArea;

Thanks for a nice article about the differences and workarounds.

I have another issue in SL that apparently doesn’t exist in WPF: I’m trying to use TemplateBinding with a gradient stop (so bind to just one particulat Color that’s part of the gradient stops collection, instead of entire gradient). It simply does nothing (no error, simply doesn’t work). I was wondering, maybe you’d have a workaround for this?

Thanks a lot!

Yes, I do need to review the project. I am actually planning to make more changes than simply getting it to work again. As you can see in David’s blog, the Charting classes are now unsealed, so now I can derive from those classes (instead of using a UserControl and a behavior, which is quite cumbersome).

In the meantime, if you need to get it working soon, you can go through the list of breaking changes listed in David’s blog. My guess is that the only one that will affect the labeled chart is the renaming of StylePalette to Palette.

Bea

PieChartLabelStyle=”{StaticResource pieChartLabelStyle}” LabelDisplayMode=”Auto” ItemsSource=”{Binding}”/>

In my project the error is in the property ItemsSource, but when I tried to regenerate your project, the error was in the property LabelDisplayMode.

Can you review the project?
Thanks!