Batch rename error with associated files

[Gwenael Q.]

Hello,

- Select "associated" files (same name, just different extension) (tested with a NEF and a Jpeg)
- Batch rename ("Tools > batch rename" or "Edit > rename")
- try to rename the files (eg. replacing part of the filename string)

=> an error message and no renaming

No wonder what setting for file association is set, this action should not raise an error. If a conflict with preference rules is detected then a window should allow user to make the good choices in the manner of what is already suggested here: viewtopic.php?f=95&t=44542&p=183699.
At the very least a warning message should be displayed but the renaming should occur.

Thanks for listening

XnVMP 1.4.2

Edit : I realize that this issue is a duplicate of viewtopic.php?f=83&t=44534
but I consider user should have freedom to override associations settings if wanted without having to dig into the preferences.


-

[xnview]

yes it's a change, now companion files are renamed correctly following 'Settings>File list - Companion'
So you think that it would be good to have an option to disable that in 'batch rename'?

[Gwenael Q.]

Hello Pierre,

The fact that XnviewMP is more and more able to manage associated files is a very good new. But I consider that the user must be able to do all kind of actions she/he wants without being blocked by computer automatisms. The machine has not to decide at the user place but assist him, helping him to make the best choices.

That's why I consider that XnviewMP should allow user to do whatever action on files. If associated files exist, a warning should be emitted to remember him that some files will perhaps become orphaned.

The settings of XnviewMP are quite obscure and challenging, documentation lacks, so making the software more comfortable with a clear interface witch leaves no doubt about what the software is doing with the images is essential.

So to answer your question I don't want XnViewMP to desable anything. I just would like a smarter help : if renaming doesn't break any association, let's rename the images without any warning. if some associations would be broken then warn the user and ask him if he want to continue or allow him to open a full control window. Once again this post is strongly related to https://forum.xnview.com/viewtopic.php? ... df92999290

Thanks for listening

[xnview]

Ok, i'll add a message...

[Gwenael Q.]

Hello,

Despite of https://www.xnview.com/mantisbt/view.php?id=2611

nothing has changed ! Error message and no renaming...

1.4.3

Thanks for listening

If renaming doesn't break any association, let's rename the images without any warning. if some associations would be broken then warn the user and ask him if he want to continue or allow him to open a full control window.

[xnview]

you don't have the message dialog?

[Gwenael Q.]

Hello,

rename issue.gif

[xnview]

and you use 'batch rename'?

[Gwenael Q.]

Hello,

Exactly same issue with batch rename :

[xnview]

what do ou have for companion settings?

[Gwenael Q.]

Hello,

Sorry for the delay.

xnviewmp companion Settings.png

Probably far from being optimized as I don't recall having found a complete explanation for these settings.

Thanks for listening

[xnview]

and you select the .nef to batch rename?

[Gwenael Q.]

Hello,

In the GIFs above you can see that I select both .jpeg and .nef

Thanks for listening

[xnview]

if you select jpg&nef, you have a warning dialog because companions are automatically renamed

[jotess]

Hello,
I'm on Windows version 1.4.5 and I believe the issue is not yet solved.
My companion file settings:

01_companion_settings.png

When I select a range of jpg files along with their RW2 companions and try to batch rename them, I get the newly introduced alert:

02_alert.png

It seems random which of the companion files are recognized as such and get removed when I hit yes.
Anyway, the result is always "The files cannot be renamed, an error occurred."
This means: No matter if I hit Yes or No and (in case of Yes) no matter if the recognized companion files are removed from the list. Only in the case that all companion files have been correctly recognized the renaming is successful.
In most cases only a few of the companions are detected, sometimes none at all.

So I believe there are different problems:

1. The alert message is not clear. At least to me. After reading this thread I understand "they are automatically renamed" means "... anyway, so they are superfluous".
2. The error message after failure is completely unclear. The list in the rename dialogue looks like everything should work fine, just the way it is expected (anyway).
3. If there is a "yes/no" option I would expect that leaving the companions in the list would render a result, too. And a result that is different from removing them from the list. So I would expect this to be a.jpg, a.rw2, b.jpg, b.rw2 -> 1.jpg 2.rw2, 3.jpg, 4.rw2.

Best regards
Joachim