For some reason acting on date in the way other than picking it from calendar doesn't change calendars view i.e. you open calendar and select current date (e.g. 25 Jul 2014). Then you change date manually e.g. using up down buttons or mouse wheel to e.g. 25 Jun 2000. Next time you open calendar you'll still see Jul 2014.
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 **
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 **
This is a bad bug - surprising it hasn't been caught/dealt with sooner. I bind a value from a dataview to the Value property and that works fine, but the date might be months in the future. User opens calendar to change that future date, but today's month is displayed and today's date is selected.
How utterly worthless that makes this control! Perhaps beggars can't be choosers but binding is rather fundamental, isn't it?
I wish I could use this control, but...