Arrow keys non-functional until focus is given to image

[VengeArturia]

On opening an image, the arrow keys will not perform their defined actions unless the image being viewed is clicked. This behavior was fine in 0.64, but seems to have been changed recently. Is there a fix for this?

[m.Th.]

On opening an image, the arrow keys will not perform their defined actions unless the image being viewed is clicked. This behavior was fine in 0.64, but seems to have been changed recently. Is there a fix for this?

Try in Tools | Settings | Interface | Keyboard for the "Left/Right" to put "Automatic" (recommended) or "Previous/next file"

[VengeArturia]

I've tried both options, neither seems to help. I always seem to have to click the image before I can do anything with the arrow keys, otherwise they simply do nothing.

[xnview]

Someone with the same problem?

[nucular]

Same problem here. Wasn't like this in the previous version.
Kind of annoying.

Edit:
Tested on Laptop and PC, both Win7 x64.
Problem only happens when the "Fullscreen when starting with a file" option in the settings is deactivated.
The arrow-symbols in the toolbar still work but to make the keyboard keys functional you still have to klick the image.

[olluz]

Same here,

really annoying.

[Lebon14]

I have registered here to say that I have the same exact issue with v0.68
I might just go back to 0.64 because it's THAT annoying.

[nucular]

Anyone know where I can download v0.64 to avoid this problem?

Edit:
Found it! - http://download.xnview.com/old_versions ... in-x64.exe
Apparently 0.66 has the Problem as well. 0.64 works though.

[nucular]

For everyone's information. This issue has already been marked as "resolved" in the bugtracker: http://www.xnview.com/mantisbt/view.php?id=361

So it should hopefully be gone in 0.69.

[Sablesword]

I've started having this problem on going from 0.64 to 0.69.

EDIT Problem only happens when the "Fullscreen when starting with a file" option in the settings is activated - the opposite of what nucular reported for 0.64

[xnview]

I've started having this problem on going from 0.64 to 0.69.

This problem is fixed in next release...