timestamp of file shifts one hour after daylight saving change

[beuvink]

When getting the file-timestamp of a file that was created during a different state of daylight saving the 'file properties' function produces a time that is shifted 1 hour compared to the actual modification time (windows explorer shows the correct time).

Did anyone experience the same issue? I will make a work-around using the DST field of the time-record function. But I do not know if the same problem happens when comparing files made in different time zones...

[DFGray]

Internally, timestamps should be saved as Greenwich Mean Time (GMT).  This is translated, on display, to the local time zone of the machine.  This is why displaying a zero timestamp give various times depending on the timezone.  It sounds like what you are seeing is expected behavior.  If you disagree, could you post an example so we can more clearly see the problem?

[waldemar.hersacher]

Look at the screen shot. Windows shows 08:41 the localtime the file was changed and LV shows 09:41.

The time the file was changed at Central Euorpean Summertine (GMT+2) and now its Central European time (GMT+1).

Message Edited by waldemar.hersacher on 11-03-2008 02:40 PM

Message Edited by waldemar.hersacher on 11-03-2008 02:42 PM

[beuvink]

I am familar with this behaviour, but this is something different.

I already included an attachement with the first post. Maybe it needs some more explanation:

- First find a file on your disk that was created during another daylight saving time (26-10-08 in the Netherlands)

- Check the timestamp for this file using windows explorer

- Select the same file in the vi and run it

- Now the timestamp has changed one hour...

When a file is selected within the current time zone, it displays the correct time.

Windows shows the correct time (it is a measurement file which includes capture-time information so I know this for sure)

[DFGray · Accepted solution]

My apologies, I misinterpreted your original post.  This behavior sounds more like a bug.  I have reported it (CAR 131938).  It is probably related to the fact that Windows, by default, sets the system time to local time, not GMT (which causes issues for those who dual boot to Linux ).  Thanks for the post.

Message Edited by DFGray on 11-04-2008 07:59 AM

[beuvink]

Thank you.

For those that may also run into this problem before it is solved, please find attached my fix. Of course I could only test it it for one daylight-save change moment