DateTimePicker lose leading 0 in milliseconds when lose focus.

[konstantine2121]

Error location

https://github.com/xceedsoftware/wpftoolkit/blob/master/ExtendedWPFToolkitSolution/Src/Xceed.Wpf.Toolkit/DateTimeUpDown/Implementation/DateTimeParser.cs

DateTimeParser.cs

private static string ComputeDateTimeString( string dateTime, string format, DateTime currentDate, CultureInfo cultureInfo, bool autoClipTimeParts )

//Has error here.
string millisecondsPart = currentDate.Millisecond.ToString();

Case

If picker has dateTime value like this '28.04.2025 16:26:16.080'

millisecondsPart = "80";

We have lost leading 0.

in the end we have a result like this '28.04.2025 16:26:16.80'

'28.04.2025 16:26:16.80' == '28.04.2025 16:26:16.800'
'28.04.2025 16:26:16.80' != '28.04.2025 16:26:16.080'

Summary

Control lost focus and value changed.

[konstantine2121]

How to reproduce this bug case

Set control Format property value = "dd.MM.yyyy HH:mm:ss" (No milliseconds in format!)

And the bound property from the ViewModel needs to have milliseconds in its value.

[XceedBoucherS]

Hi,

Thank you for reporting this.

Here's a quick fix:
Go in file: Xceed.Wpf.Toolkit/DateTimeUpDown/Implementation/DateTimeParser.cs
In method : ComputeDateTimeString()
near the end, and add
while( millisecondsPart.Length < 3 )
{
millisecondsPart = "0" + millisecondsPart;
}
just before the line:
time += "." + millisecondsPart;

This will make sure 80ms is not transformed in 800ms in the DateTime.TryParse() call.

This will be fixed in a future release.
Thank you