XnView Software

In XnView's config section "Viewer > Info", you can set the display of a line containing various definable details about the current viewed file. The shortcut command is named 'cmd_showInfo', its keyboard shortcut defaults to the letter "I".

For example, when resizing an image, the active info line would display the new image dimensions automatically. I think it started with XnView v1.8.3 when the info line is no longer updated dynamically, and I have to toggle the info display off and on again to have it show the updated image dimensions.

it works here, please describe how to reproduce?

xnview wrote: Mon Oct 27, 2025 6:56 am it works here, please describe how to reproduce?

Because you just confirmed the info line to be fully working for you, I rechecked my settings. I started by replacing my individual info-line config with XnView's default string.

1. Back to square one:

With XnView's default info-line configuration (see code below), the display of the info-line is working again as intended, including the dynamic display of any image dimension changes. That's a good start.

2. Investigating the issue:

Then I started to edit the default info-line config, removing one item at a time, and restarting XnView after each change, to slowly shape the info-line back to my previous individual setup.

As soon as I remove the entry "{Zoom}" from the info-line configuration, the changes to the image dimensions aren't dynamically displayed anymore. Now I have to toggle the info-line off and on by pressing the keyboard shortcut "I" twice to see any changes I made to the image dimensions.

Now adding back the entry "{Zoom}" to the info-line configuration, at any position in the config line, has the dynamic display of changes to the image dimension working again.


3. Conclusion:

This simplified info-line configuration will display any changes to the image dimension dynamically: Removing the entry "({Zoom}%)" from this simplified configuration breaks the display of any dynamic image dimension changes:

Thanks to your detailed description I can reproduce the problem.