Maybe its not a bug but here is an example when it has bad visual experience: you have Value property of DateTimePicker bound to property in data context which is initially unset i.e. 1 Jan 0001. When you change the value of the property the date displayed is correct but when you open calendar you'll see Jan 0001 and you have fun time moving to something closer to present time
Comments: ** Comment from web user: jcCodePlex59 **
Thanks for your reply.
<I don't see where emartin says it's fixed in 2.4 -- I have v2.2.0.0, which I just downloaded yesterday so I don't know where to get 2.4>
My code looks like this:
```
<xceed:DateTimePicker Name="dtpEndTime" Value="{Binding EndTime}" Format="Custom" FormatString="dddd, MMMM, dd, yyyy" Grid.Row="1" Grid.Column="1" HorizontalAlignment="Center" ></xceed:DateTimePicker>
```
And the results I get depend on a couple of factors.
1. If my bound date (in a listview gridview) is in the past, the control displays todays date:

2. For a future date, the calendar always displays the date of the first record displayed:

as if the variable used was static or I'm not getting a new object for each data row in the list.
(Feb 23, 2015 is the date on the first row loaded).
Thanks!