I discovered a couple of problems with the XamDateTimeEditor.
The suggested solution for my previous question does not work if there is a binding to the value of the XamDateTimeEditor control.
Please see the attached solution that explains the problems in detail.
A Date can be picked from the MonthCalendar drop down, but it is always flagged as invalid with a red border.
European Dates cannot be entered if the day of the month is greater than 12.
Could you please help me with the identified problems?
Hi Petar
The suggested approach does work. Thank you.
Hello ,
I am just checking the progress of this issue and was wondering if you managed to achieve your goal or if you need any further assistance on the matter.
If the above suggestion helped you solve your issue please verify the thread as answered so other users may take better advantage of it.
Hello,
I have been looking into your issue and the issue was fixed in order to work in the common scenario - without an IValueConverter. In your particular scenario the converter’s ConvertBack method should return a DateTime value, so I can suggest a convert method like this one:
public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
{
if (value != null)
if (value.ToString().ToLower() == "now")
return DateTime.Now;
}
DateTime date;
if (value == null)
return null;
else if (DateTime.TryParse(value.ToString(), out date))
return date;
else
in order to see the fix in action.
Please let me know if you require any further assistance on the matter.
I have been looking into this and I am also still able to reproduce this, so I am going to contact development to see if anything is a miss.
I'll update you shortly with my findings.
Today I received an email from Infragistics Support
"Issue "77173: Invalil value error when mask="CCCCCCCCC" and the editor's value is bound" has been addressed in service release versions WPF_11.1.20111.2026, WPF_10.3.20103.2237, WPF_10.2.20102.2341"
I downloaded and installed the service release. I found the issue listed in the FixedBugs pdf.
But when I test the problem in the sample solution I uploaded (with updated references to the service release assemblies), the problem still exists unchanged. Was the fix not tested with the provided solution?