Page 1 of 1

Companion bug in "Batch rename"

Posted: Sun Mar 22, 2020 11:12 am
by mpy
As requested in the Companion bug thread (viewtopic.php?f=104&t=39613#p161599) I post this as a new bug.

XnViewMP 0.96 64bits (Mar 20 2020)
OS: Linux (Arch)

I experience issues with breaking the linkage between files and their companions when using the Batch rename tool.

My settings for companion files are

[ ] - Show Companion
[x] - Delete
[x] - Copy/move/Rename


1) Initial directory content (please note for one file pair the extension's case is JPG, for the other it's jpg)

Code: Select all

DRX00998.JPG
DRX00998.JPG.xmp
DRX00999.jpg
DRX00999.jpg.xmp
2a) Use Batch rename with Extension option activated and set to e.g. "jpg".
or
2b) Use Batch rename with Case option activated and set to something involving the extension, e.g. "Extension lowercase".

Directory content is in both cases now:

Code: Select all

DRX00998.jpg
DRX00998.JPG.xmp
DRX00999.jpg
DRX00999.jpg.xmp
=> Broken linkage between file and companion, when the master file had an upper case extension.

Expected behavior: Companion file renamed to DRX00998.jpg.xmp.

Thanks a lot!

Re: Companion bug in "Batch rename"

Posted: Wed Feb 02, 2022 1:41 pm
by xnview
:bugconfirmed: Thanks to your detailed description I can reproduce the problem.

Re: Companion bug in "Batch rename"

Posted: Mon Mar 28, 2022 10:12 am
by xnview
This problem is supposed to be fixed in XnView MP 1.00 beta. Please check and confirm the bug fix here.

Re: Companion bug in "Batch rename"

Posted: Mon Mar 28, 2022 6:13 pm
by mpy
Thanks a lot for addressing this issue. :D I'm more than happy to check the fix, but unfortunately at the moment I can't -- as I use neither a Mac, nor a Windows machine. I will watch the beta release post and will test as soon you will release a beta version for Linux.

Re: Companion bug in "Batch rename"

Posted: Wed Apr 13, 2022 6:49 pm
by mpy
I can confirm that this bug is fixed in XnView MP 1.00! 8)
(To be more precise, I tested the Linux version of XnView MP 1.00 beta 3)
Thanks a lot :D