shell properties time discrepancies

Things you’d like to miss in the future...
Post Reply
jupe
Posts: 2757
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

shell properties time discrepancies

Post by jupe »

There seems to be some bogus returns of the hours from time shell properties (via the various methods of retrieval eg. property()), this may only apply to my locale I am not sure, but for example I get the hours between these 2 properties (and other time date ones, like DateModified etc) to be always returned incorrectly for shell props, whereas XY special props shows the correct values. (I don't mean the formatting) eg,

text report("{Name}<crlf>{prop:System.Photo.DateTaken}<crlf>{prop:#image.datetaken}<crlf 2>", 1);

2021-07-31_072515.png
2021-07-31_072515.png (1.11 KiB) Viewed 401 times
The bottom hour value is the "correct" one, maybe UTC offset isn't being applied?

RalphM
Posts: 1932
Joined: 27 Jan 2005 23:38
Location: Cairns, Australia

Re: shell properties time discrepancies

Post by RalphM »

I can confirm this, I get the below with UTC+10:

Code: Select all

IMG_1274.JPG
30/10/2019 05:38:41
30/10/2019 15:38:41
Ralph :)
(OS: W11 22H2 Home x64 - XY: Current beta - Office 2019 32-bit - Display: 1920x1080 @ 125%)

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: shell properties time discrepancies

Post by admin »

The same issue is also true for prop:WhenTaken. I noted that somewhere deep down in the change log:

Code: Select all

v11.30.0104 - 2012-06-17 15:15
      ...
      Note that the numeric property identifier "#25" is preferred to 
      the verbal "WhenTaken" because the latter returns the time in UTC 
      (Coordinated Universal Time) instead of local time -- a mysterious 
      shell anomaly.
I could silently correct this anomaly, however, that might break old user code... hmmm... :maf:

Post Reply