Jump to content

Recommended Posts

I want to check if this is a bug before posting in the Bug Tracker. I've searched the bugs and changes and found nothing.

I have a file. In Windows (8.1) properties dialog, it states the modification time is: 27 ‎December ‎2014, ‏‎21:53:35


This is correct. I have a record of this information elsewhere, which we will be referring to. If I run this code:

$ftime = FileGetTime($file)
PrintArray($ftime,  "$ftime", 0, @ScriptLineNumber)

I get:

.\test.au3(21) : ==> $ftime:
[0] : 2014
[1] : 12
[2] : 27
[3] : 22
[4] : 53
[5] : 35

Precisely one hour later than the correct time.

My current locale is United Kingdom, and we are currently experiencing "British Summer Time", though this should have no effect on the modification time of the file, which is December.

Because of what quacks like a bug, when my program examines this file's modification date, it sees that it is one hour older than its corresponding record (which is correct), and so considers the file modified, which it isn't, as reported by Windows Explorer et al.

AutoIt seems to be adding an arbitrary hour to its time output because we are inside British Summer Time. But that's just a hunch.

I'm using AutoIt v3.3.12.0 on Windows 8.1 x64.

;o) Cor

nothing is foolproof to the sufficiently talented fool..

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...