Although I don't think it is a workaround, there is a way to get it to behave properly: After making a date selection via the calender itself, it seems to "wake it up"; after that it seems to stay synchronized with the Value property.
Comments: ** Comment from web user: BCA011 **
Hi,
I just upgraded to v2.4 (community edition), and this issue has not been resolved (at least, completely). What I'm finding is that the drop-down calender has a grey square behind today's date and a blue square behind the date bound to the ```Value``` property. I have confirmed that the blue square is indeed synchronizing with Value--but only when it happens to land on the same month display as today's date. For example, today is March 9th. If I load my app and set the Value property to March 3rd, then open the drop-down calender, everything is fine: the 9th has a grey square and the 3rd has a blue square. Then if I click Down on the spinner a few times I move backwards into February. Then I open up the calender and things are still fine because March's display includes the last week of February. The problem occurs when I down-spin or databind that Value property back to mid-February: upon opening the calender, the blue square is no longer visible. It seems like the highlighting of today's date is the priority.
Is there a way to change this priority? Or turn off the highlighting of today's date altogether?
Thanks