Hello there!
I've came across an odd UI behavior.
Dialog box "Find files".
When I enter a date and time from the (former here) daylight saving period and then press the ">>" button, I see an hour difference in the "Date" dialog box.
I use a fully updated W7 Pro x64, TC 8.51a x86, time zone is set to RTZ2 (Moscow, UTC+03:00).
Daylight saving was cancelled in Russia a few years ago and last autumn Moscow's time zone was changed from UTC+4 to UTC+3.
Image: http://i.imgur.com/FqdcHzV.png
Actually, TC uses for searching the data taken from main search dialog box, not from the "Date" box.
Is this discrepancy a bug or it's just related to MS way of time conversion?
Best regards,
Rainie.
[TC 8.51a] A daylight saving UI bug?
Moderators: Hacker, petermad, Stefan2, white
[TC 8.51a] A daylight saving UI bug?
#197063 Personal licence
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
This should be fixed in 8.52 beta 1, please test it! Make sure to test a date not within daylight saving time, e.g. 1.1.2015 10:00. The error only occurs when the current date uses daylight saving time and the entered time does not, or vice versa.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Seems to be fixed in 8.52b1.
By the way, in 8.51a entering any date up to 25.10.2014 (the actual date of clock adjusting here) leads to the bug, however, TC uses the date filled in the Search dialog for search purposes. So, "1.1.2015 10:00" works fine even in 8.51a, but "1.1.2014 10:00" does not.
8.52b1 works as intended.
We do not adjust clock twice per year since autumn of 2011, actually we've just switched from constant UTC+4 (for Moscow timezone, established in 2011) to UTC+3 (for Moscow timezone, established in 2014). The latest MS timezone patch has updated Windows' TZ table according to the local law (RTZ2, UTC+3 for Moscow) and TC revealed such behavior.
P. S. Thanks for your hard work and good luck with TC 9.
By the way, in 8.51a entering any date up to 25.10.2014 (the actual date of clock adjusting here) leads to the bug, however, TC uses the date filled in the Search dialog for search purposes. So, "1.1.2015 10:00" works fine even in 8.51a, but "1.1.2014 10:00" does not.
8.52b1 works as intended.
We do not adjust clock twice per year since autumn of 2011, actually we've just switched from constant UTC+4 (for Moscow timezone, established in 2011) to UTC+3 (for Moscow timezone, established in 2014). The latest MS timezone patch has updated Windows' TZ table according to the local law (RTZ2, UTC+3 for Moscow) and TC revealed such behavior.
P. S. Thanks for your hard work and good luck with TC 9.
Last edited by Rainie on 2015-08-12, 10:27 UTC, edited 2 times in total.
#197063 Personal licence
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact: