Hello,
I would like to request a feature or setting regarding how XnView handles the internal file list position after performing a "Save As" operation.
My Workflow:
I am performing manual edits (like cropping) on a folder of images. I go through the list one by one, edit an image, and save it as a new file (Save As).
The Issue:
Currently, as soon as I save the new image, XnView automatically updates the internal file list and moves the focus/index to the newly created file.
- If I save in the same folder: The viewer index jumps to the very end of the queue where the new file was created. If I was in the middle of a large list (e.g. image 50 of 100), I am now at position 101. If I press "Next", nothing happens (or it loops), and to continue my work I have to navigate all the way back to image 51.
- If I save to a different folder: I tried this as a workaround. However, XnView immediately switches the context to the target folder. This is actually worse, as I completely lose my place in the source folder.
I am looking for behavior similar to IrfanView.
In that program, when you save a new copy, the screen obviously still shows the edited image you just saved. However, the internal file list position does not jump to that new file.
If I press "Next" or "Previous" in IrfanView immediately after saving, it navigates relative to the Original Source Image, not the new file. It remembers where I was in the queue.
The Request:
Could you please add a setting to "Keep file list position on original file after Save As"?
I don't mind if the new file is added to the database/file list in the background, but I need the active navigation pointer to stay where it was so I can continue to the next image in my workflow without losing my place.
Thank you!
