1.8.2: date type for viewer in the status bar uses the browser's date type

Older bugs which are supposed to be fixed in 0.84. *** Please try to reproduce your bug and confirm the bug fix. ***

Moderators: XnTriq, helmut, xnview, Dreamer

100
Posts: 1
Joined: Mon Oct 28, 2024 8:24 am

1.8.2: date type for viewer in the status bar uses the browser's date type

Post by 100 »

XnView: MP 1.8.2 64-bit
OS: Windows 10 64-bit

The setting for the viewer, which date should be shown in the status bar, does not work. The status bar of the viewer always shows what is set as the date type for the browser. Both therefore use the date type that is set for the browser.

To reproduce:
  • Use a photo with Exif data.
  • Activate the date display in the status bar for the viewer.
  • Select all 4 options from the drop-down menu one after the other and view the same image after each selection. The display does not change. What is displayed is always what is set in the browser drop-down menu.
  • Now select all 4 options from the drop-down menu for the browser date one after the other. It does not matter whether the date for the browser is activated or not. After each selection, also look at the same photo there and compare the date in the status bar with those in the properties of the photo (also Exif). It matches the properties. The drop-down field setting for Viewer has no effect. Only the checkbox whether a date is active or not works correctly.
XmView MP_1.8.2_statusbar_viewer_date_bug.jpg
You do not have the required permissions to view the files attached to this post.
User avatar
xnview
Author of XnView
Posts: 44936
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: 1.8.2: date type for viewer in the status bar uses the browser's date type

Post by xnview »

:bugconfirmed: Thanks to your detailed description I can reproduce the problem.
Pierre.
User avatar
xnview
Author of XnView
Posts: 44936
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: 1.8.2: date type for viewer in the status bar uses the browser's date type

Post by xnview »

This problem is supposed to be fixed in XnView MP 1.8.3. Please check and confirm the bug fix here.
Pierre.