Page 1 of 1

0.99.7 & 1.0: statusbar 'file date' does not match settings

Posted: Thu Aug 11, 2022 7:26 pm
by kbyork
XnView: MP 0.99.7 & 1.0 64 bit
OS: Windows 7 Pro. 64bit

I tried using:
SETTINGS > BROWSER > StatusBar > FILE-DATE = EXIF date taken
SETTINGS > BROWSER > StatusBar > FILE-DATE = EXIF date modified
but did not get expected results.

Effect: statusbar return incorrect file date info.

To reproduce/(TEST for error):
1. I took an image without metadata and used FileTime_x86.exe to give the image different file dates for CREATED, MODIFIED and ACCESSED
2. made a copy of image.
3. I used ExifTool.exe to give the second image, metadata with different dates for EXIF DateTimeOriginal, EXIF CreateDate, EXIF ModifyDate.
4. I used XnViewMP's INFO pane (Exiftool TAB) to verify I did this correctly.
5. Then checked the statusbar when selecting each file; with setting 'FILE-DATE = EXIF date taken'
6. Repeat with setting 'FILE-DATE = EXIF date modified'

Actual behaviour (bug): my test showed: :bug:
  • file with metadata:
    • FILE-DATE = "EXIF date modified" returned EXIF Image Date-taken
    • FILE-DATE = "EXIF date taken".... returned EXIF Camera Date-modified
  • file without metadata:
    • FILE-DATE = "EXIF date modified" returned File date MODIFIED
    • FILE-DATE = "EXIF date taken".... returned File date MODIFIED
Expected behavior:
  • file with metadata:
    • FILE-DATE = "EXIF date modified" returns EXIF Camera Date-modified
    • FILE-DATE = "EXIF date taken".... returns EXIF Image Date-taken
  • file without metadata:
    • FILE-DATE = "EXIF date modified" returns File date MODIFIED
    • FILE-DATE = "EXIF date taken".... returns File date CREATED

Re: 0.99.7 & 1.0: statusbar 'file date' does not match settings

Posted: Wed Aug 17, 2022 3:13 pm
by xnview
:bugconfirmed: Thanks to your detailed description I can reproduce the problem.

Re: 0.99.7 & 1.0: statusbar 'file date' does not match settings

Posted: Wed Aug 24, 2022 12:49 pm
by xnview
This problem is supposed to be fixed in XnView MP 1.02. Please check and confirm the bug fix here.