This is what happens when two Toolkits fall in love... [The February 2010 release of the WPF Toolkit is now available!]

**

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
  February 22, 2010
  Hi, any news on the WPF ribbon? Thanks, Mathias

• Anonymous
  February 22, 2010
  Hi Mathias, We've been heads down with WPF 4.0 work, but we've recently been able to resume our development efforts on Ribbon.  We’re looking to release a new version in the first half of 2010, shortly after the release of Visual Studio 2010. -Saied

• Anonymous
  February 22, 2010
  The comment has been removed

• Anonymous
  February 23, 2010
  shaggygi, Your passion is great to see! :) I think additional controls will be ported over as time and resources permit. I don't have any particular insight into when some of this might happen, but I'm going to pass your feedback on to some of the relevant folks internally to be sure these issues are on their list. Thanks for the feedback!

• Anonymous
  March 04, 2010
  I think it is incredibly important that WPF and Silverlight stay as consistent as possible. So where practically possible controls  and themes should be in both toolkits and be as consistent as they can be. Missing the lovely BusyIndicator in particular!!! Keep up the good work....

• Anonymous
  March 05, 2010
  NickWhymark, Thanks for your feedback, I'll do what I can to help here! :)

• Anonymous
  March 31, 2010
  The comment has been removed

• Anonymous
  April 01, 2010
  maverickcoder, It ought to be possible. :) There are some people who have written about creating new series types - you can find all the posts I know about in my charting links collection here: http://cesso.org/r/DVLinks Hope this helps!

• Anonymous
  April 05, 2010
  Hi, I am trying like this creating step line data from normal keyvalue pair. But sometime it creates step line for few points in chart and sometime not. Donot knw why this strange behaviour. <chartingToolkit:Chart x:Name="Chart1">  <chartingToolkit:Chart.Series>    <chartingToolkit:LineSeries Title="S1" IndependentValueBinding="{Binding Path=Key}"        DependentValueBinding="{Binding Path=Value}">    </chartingToolkit:LineSeries>  </chartingToolkit:Chart.Series> </chartingToolkit:Chart> Code: ......  List<KeyValuePair<int, int>> series = new List<KeyValuePair<int, int>>();  series.Add(new KeyValuePair<int, int>(10, 100));  series.Add(new KeyValuePair<int, int>(20, 130));  series.Add(new KeyValuePair<int, int>(30, 150));  series.Add(new KeyValuePair<int, int>(40, 125));  series.Add(new KeyValuePair<int, int>(50, 155));  ((LineSeries)Chart1.Series[0]).ItemsSource = CreateStepLineSeries<int, int>(series); ...... List<KeyValuePair<T, U>> CreateStepLineSeries<T, U>(List<KeyValuePair<T, U>> source) {  List<KeyValuePair<T, U>> returnValue = new List<KeyValuePair<T, U>>();  for (int i = 0; i < source.Count; i++)  {    KeyValuePair<T, U> currentValue = source[i];    returnValue.Add(currentValue);    if (i < source.Count - 1)    {      KeyValuePair<T, U> nextValue = source[i + 1];      returnValue.Add(new KeyValuePair<T, U>(nextValue.Key, currentValue.Value));    }  }  return returnValue; }

• Anonymous
  April 06, 2010
  maverickcoder, LineSeries sorts its point by IndependentValue, but when two points have the same value, they may not always maintain their original order. I think I've seen someone trying to do the same thing and what worked for them was to make sure the new points they added were had slightly different IndependentValues. This ensured that they would always sort deterministically in the intended order and gave the pretty step effect they wanted. Maybe give that a try?

• Anonymous
  April 06, 2010
  The comment has been removed

• Anonymous
  April 06, 2010
  I am trying to remove the dot from the lines in the line chart. But it becomes orange if I change the template of the line. Then legend is of no use as all line turns orange. <Style x:Key="EmptyPointsStyle" TargetType="{x:Type DVC:LineDataPoint}">      <!--<Setter Property="Template" Value="{x:Null}"/>-->      <Setter Property="BorderThickness" Value="1"/>      <Setter Property="Template">        <Setter.Value>          <ControlTemplate TargetType="DVC:LineDataPoint">            <Ellipse StrokeThickness="{TemplateBinding BorderThickness}"/>          </ControlTemplate>        </Setter.Value>      </Setter>    </Style> <Style x:Key="EmptyPointsStyle" TargetType="{x:Type charting:LineDataPoint}">      <Setter Property="BorderThickness" Value="1"/>      <Setter Property="Template">        <Setter.Value>          <ControlTemplate TargetType="charting:LineDataPoint">            <Ellipse StrokeThickness="{TemplateBinding BorderThickness}"/>          </ControlTemplate>        </Setter.Value>      </Setter>    </Style> <charting:LineSeries Title="Light" x:Name="myLightChart" DataPointStyle="{StaticResource EmptyPointsStyle}"             IndependentValueBinding="{Binding Path=Key}"             DependentValueBinding="{Binding Path=Value}"> </charting:LineSeries> Is this bug ? or any turn around?

• Anonymous
  April 06, 2010
  maverickcoder, I discuss the underlying issues here: http://blogs.msdn.com/delay/archive/2009/05/19/chart-tweaking-made-easy-how-to-make-four-simple-color-tooltip-changes-with-silverlight-wpf-charting.aspx Basically, once you decide to customize the DataPointStyle, that custom Style overrides the automatic Style from the Chart.Palette collection and therefore the custom palette color doesn't get applied and the DataPoint reverts to its default orange color. You can provide a specific Background in your custom Style or copy the default Palette as I describe in that post. Hope this helps!