DateTimePicker ... difference between the properties text and value

Hi Harald, Nic,

the fix for WJ-8455 is included in the latest Wisej release (1.4.32).

Best regards
Frank

Hi Nic,

most likely yes. The problem was not directly related to a specific locale but to entering the value directly inside the DateTimePicker control.

Please contact me at frankATiceteagroup.com if you want to have a prerelease to verify the fix prior to the next release.

Best regards
Frank

Hi Frank / Luca,

I think I have a similar issue to this using UK browser locale. Any attempt to manually enter a time into the datetime picker results in an invalid value being returned.

Is this the same issue as described by Harald?

Thanks

Nic

Hi Harald,

thanks again for getting back on this. We rechecked and could finally reproduce.
The bug is logged as WJ-8455 and a fix will be included in the next Wisej release.

We´ll inform you when it´s available.

Best regards
Frank

Hi Frank,

I’m using German versions … OS (Windows 8.1), Browsers (Chrome, Internet Explorer, Firefox – newest versions).

I’m not sure but I think that this behaviour of the date time picker is quite new.

Best regards,

Harald

Hi Luca,

thank you for your reply.

I modified your example a little bit … you can see the differences when you

1. Input “01.10.2017” and click the button -> you can see the same result of datetimepicker’s properties “.text” and “.value”
2. Input “31.12.2017” and click the button -> you can see a different result … when you click the icon of the datetimepicker after that then you can see that the control is in a “confused/undefined state”

Best regards,

Harald

Hi Harald,

can you please check your browsers language settings ? I could exactly reproduce the behavior when I tried on a german OS with en-US locale in Chrome.

Best regards
Frank

Do you use a custom format?

I have attached a small test case that I just used but cannot reproduce. I added ?lang=de to make the session use the de-DE locale.