tc.creationdate.D.M.Y h:m:s bug

[DrShark]

From forum.wincmd.ru
When file has odd number in seconds in creation time, tc.creationdate.D.M.Y hs make it 'even' (example: displays 22 instead of 23). But the field tc.creationtime.hs shows time correctly.

[ghisler(Author)]

TC 7 uses the FAT(32) date/time internally. TC 7.5 will use the NTFS time, it has already been changed.

[Hacker]

Christian,
Hoorray!

But the question is - how come TC displays an odd seconds number? I thought the FAT32 format only allowed for even numbers.

Roman

[DrShark]

2Hacker
Hi!
1. While discussing thread on russian forum, one user reffering to a russian translation of MS FAT32 srecification was approving that seconds in CREATION date/time on FAT32 can be odd...
2. Regardless where is a truth, tc.creationdate.D.M.Y hs and tc.creationtime.hs works different!

2ghisler(Author)

TC 7 uses the FAT(32) date/time internally. TC 7.5 will use the NTFS time, it has already been changed.

Sorry, NTFS date/time on FAT32... How?

[ghisler(Author)]

Creation time is read directly from the file only when needed, by the internal 'tc' plugin. This plugin uses the native date/time of the file system. Creation date is converted to internal format first.

[DrShark]

Christian, sorry, it's still not clear enough for me.
I created 2 columns:
[=tc.creationdate.D.M.Y hs], value: 22.08.2007 22:16:42
[=tc.creationtime.hs], value: 22:16:43

So this is not a bug?
But... Maybe I would agree with you, TC has not column [=tc.creationdate.D.M.Y creationtime.hs], but user still can use [=tc.creationdate.D.M.Y] + [=tc.creationtime.hs]... Please tell your point.

[ghisler(Author)]

It's not a bug, it's a limitation of how TC currently works. The next big release, 7.5, will use the NTFS time internally, so there will be no more such problem.

[DrShark]

Fixed in TC 7.5.

[ghisler(Author)]

Thanks!