1.8.2 - Viewer - tag/untag keyboard shortcut unreliable for animated GIFs

[marp]

XnView: MP 1.8.2 . 64-bit
OS: Linux (Ubuntu 24.04)

A keyboard shortcut can be defined for tagging and untagging images (toggling the tag on and off with same keyboard shortcut).
This shortcut can be defined separately for browser and viewer.
In this case, the same shortcut (CTRL-F4) has been defined for both browser and viewer.

Shortcut works perfectly for browser.

With 1.8.2, shortcut does NOT work reliably for viewer when viewing animated GIFs.
Sometimes (less than half the time), the shortcut works in viewer mode.
More likely (more than half the time), the defined shortcut will NOT toggle/flip the tag on the viewed animated GIF image.

This effects viewer-mode (fullscreen), only.
This only seems to happen with animated images (observed only with animated GIFs, not tested with animated WEBP).
This happens intermittently. Not all animated images are always affected, and it is not always the same animated images. However, this appears to happen for more than 50% of all viewed animated GIFs.
This faulty behaviour was not observed with previous versions. However, it might simply have been missed to notice, at the time.

To reproduce:
1. Have a folder with a few dozen animated GIF images
2. Select folder and enter fullscreen viewer mode (e.g. via F11, or via ENTER, if configured for fullscreen viewing)
3. Scroll through files one by one, e-g- by using mouse wheel
4. Tag/Untag viewed file by using configured keyboard shortcut (CTRL-F4 in my case).

Actual behaviour (bug): For some of the animated GIFs, the keyboard shortcut will do nothing. No tagging/untagging of the image.

Expected behaviour: Reliable tagging/untagging of images via keyboard shortcut.


Best Regards,
Marp.

[xnview]

Thanks to your detailed description I can reproduce the problem.

[marp]

Thank you - much appreciated.
Looking forward to 1.8.3.

[xnview]

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

[marp]

Confirmed - I am unable to reproduce the issue with 1.8.3.

Many Thanks.