The one with all the goofy heading names [Detailed information about the Silverlight Toolkit's new stacked series support]
**
This blog has moved to a new location and comments have been disabled.
All old posts, new posts, and comments can be found on The blog of dlaa.me.
See you there!
Comments
Anonymous
April 16, 2010
niceAnonymous
May 11, 2010
The comment has been removedAnonymous
May 12, 2010
The comment has been removedAnonymous
May 12, 2010
Hi Delay, Fantastic, it is great to wake up to some fresh ideas on how to address my problem, thank you for your help. I have set the opacity in the ControlTemplate of the DataPointStyle and have extracted the StackedColumnSeries control template, but I am unclear as to what you mean by "ensure it has generated its containers", and when you say use it's ItemContainerGenerator do you mean a method in codebehind. Thank you for your help.Anonymous
May 12, 2010
codekiwi, I'm referring to the ItemsControl.ItemContainerGenerator property: http://msdn.microsoft.com/en-us/library/system.windows.controls.itemscontrol.itemcontainergenerator(VS.96).aspx If you're not familiar with the concept, here's a good write-up by Dr. WPF (it's for WPF, but most of the concepts are the same for Silverlight): http://drwpf.com/blog/2008/07/20/itemscontrol-g-is-for-generator/ In particular, the section "Dealing with Asynchronous Container Generation" discusses the topic I was referring to.Anonymous
May 12, 2010
Haha that is so funny, I was reading that exact article (well it's predecessor 'I is for Itemcontrol') as you posted that. Thanks for your help, I will see how I go.Anonymous
July 19, 2010
The comment has been removedAnonymous
July 20, 2010
The comment has been removedAnonymous
July 20, 2010
Thanks for the advice - I'll give it a try and let you know if i land anything worth sharing. KevinAnonymous
October 20, 2010
The comment has been removedAnonymous
October 21, 2010
Andreas, The DefinitionSeries.SeriesDefinitions collection-typed property is deliberately not a DependencyProperty (for the same reason that Chart.Axes isn't; you can read more about why here: cesso.org/.../DTDPDEFSHARE). Because Binding only works with DependencyProperties, I suspect this is the reason for the trouble you've had so far. That said, the Chart.Series property is the same kind of thing, so I'd expect that if you take the same approach Beat writes about in the link you reference (subclassing and adding a DependencyProperty for Binding), it would work for this scenario as well (except in this case you'll subclass StackedBarSeries instead of Chart). If you try this, I'd love to hear how it works out! (But if not, then you should always be able to create the SeriesDefinitions in code - you just won't be able to leverage Binding the same way.)Anonymous
November 01, 2010
The comment has been removedAnonymous
January 19, 2011
Hi Delay, it is possible that StackedSeries removed from WPF Toolkit, because I get the error that StackedBarSeries not exists in 'clr-namespace ...DataVisualization.Toolkit'. I used v3.5.40128.1.Anonymous
January 20, 2011
The comment has been removedAnonymous
March 12, 2011
One thing I was using in the old column/bar stack was that it would squish multiple columns into the same category. Now it seems to try and do a stack column/bar but with data from several data series, so instead it overlaps based on the series index.Anonymous
March 13, 2011
The comment has been removed