While playing around with some custom columns I noticed that TC doesn't show dates beyond the year 2559 although I was sure and confirmed the dates I fed to TC were beyond that year, e.g. added a message box to one of my WDX plugins, and consulting other applications.
Here's how to reproduce the behavior I observed:
- Create a file in TC, e.g. with Shift+F4
- Get NirSoft BulkFileChanger (BFC)
- Open BFC and open the newly created with F2 (Add Files)
- Select the file in BFC and then press F6 to open the "Change file time /attributes" dialog
- Enable the checkbox "Modified" and set the date to 31.12.2559 and click the "Do it" button
- Check date/time of this file in TC, you'll see the correct date
- In BFC, press F6 again and set the Modified date to 01.01.2560 and confirm the changes
- Back in TC, check the date, you'll notice it shows 01.01.2559
The only thing related I could find is the thread NewTimeZoneMethod bug where Ghisler stated that
OK, that explains the observed behavior. But I cannot confirm any crashes or other weird behavior when calling this function. It worked everytime I tested this, be it on Win2k, WinXP (SP3) or Win7 (SP1). Actually, I tested the year 3015 because that's the value my WDX plugin returned to TC, but I don't think that's relevant considering Ghisler's explanation quoted above.https://www.ghisler.ch/board/viewtopic.php?p=332882#p332882 wrote:SystemTimeToTzSpecificLocalTime crashes when the year is >=2559. I will therefore not call this function when the year is that high.
Now I'm aware that this topic is rather academical (hence I didn't post it in bug reports section) because who knows if mankind is still around, and using TC - or even computers at all - when the time comes, but I'm a fan of showing correct values/output nonetheless.
Regards
Dalai