Left and Right Arrow Behaviors Contrary to Expectations

[speedoops]

Hi, I encountered a minor issue.

For example, three are three images in the folder: image1.png, image 2.png and image3.png. Currently, image2.png is open.

When pressing the left arrow key:

• In void image viewer, it shows the next image, i.e. image3.png;
• In windows built-in image viewer, it shows the prev image, i.e. image1.png.

When pressing the right arrow key:

• In void image viewer, it shows the prev image, i.e. image1.png.
• In windows inner image viewer, it shows the next image, i.e. image3.png;

So, the actions of the void image viewer are different from those of windows built-in image viewer, which is inconvienent.

I was wondering if you can make the void image viewer behave the same as windows built-in one, or perhaps add a configuration option for this.

Thanks for sharing this wonderful app!

[voidtools]

voidImageViewer normally shows images in order of date modified.

Please try setting your sort order to name:
In voidImageViewer, from the Navigate menu, under the Sort submenu, check Name.

Does the issue persist?

[speedoops]

voidImageViewer normally shows images in order of date modified.

Please try setting your sort order to name: In voidImageViewer, from the Navigate menu, under the Sort submenu, check Name.

Does the issue persist?

Oh, I see! After following the method you provided, the problem was solved. Now it works like a charm.

However, why isn't it sorted in ascending order by file name by default?

[voidtools]

I have put on my TODO list to use the sort order from Windows Explorer, from where the images was opened.

[speedoops]

I have put on my TODO list to use the sort order from Windows Explorer, from where the images was opened.

Using the sort order from Windows Explorer is actually a pretty good idea, I just found out that's how the Windows built-in image viewer does. You really make the software with heart!

I think i should keep this issue open (until we start using the sort order from Windows Explorer), even though my problem's been solved. Other people might run into the same issue, and leaving it open will help them find the solution quicker. Buf if you think it's more suitable to close this issue since we‘ve got a workaround, you're more than welcome to go ahead.