[0.89] Name collision dialog uses old name on renaming

Older bugs which are supposed to be fixed in 0.84. *** Please try to reproduce your bug and confirm the bug fix. ***

Moderators: XnTriq, helmut, xnview, Dreamer

Post Reply
JMM72
Posts: 33
Joined: Wed Feb 10, 2016 2:16 pm

[0.89] Name collision dialog uses old name on renaming

Post by JMM72 »

XnView: MP 0.89 - 64 bit
OS: Windows 7 64bit

When renaming a file, if the new name already exists, the name collision dialog suggests an unique name like 'copy of <file.ext>'. However, it suggest the old, original name, instead of using the new name used when trying to rename.

Effect: While the effect is minor, it wastes time and/or data, as you can't go back to the renaming dialog to edit, nor you have the new name you have typed anywhere.

To reproduce:
1. Use a folder with two files, e.g. 'old.jpg' and 'new.jpg'.
2. Select 'old.jpg' and rename (with F2) to 'new.jpg'.
3. The collision dialog appears suggesting to replace the existing file with the renamed one, or to rename again to 'copy of'.
4. The suggested name is 'copy of old.jpg', instead of 'copy of new.jpg'.

Actual behaviour (bug): the suggested name is based on the original name 'copy of old.jpg'

Expected behaviour: the suggested name should be based on the newly renamed name (the name of the already existing file) 'copy of new.jpg'.
User avatar
xnview
Author of XnView
Posts: 43357
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: [0.89] Name collision dialog uses old name on renaming

Post by xnview »

:bugconfirmed: Thanks to your detailed description I can reproduce the problem.
Pierre.
User avatar
xnview
Author of XnView
Posts: 43357
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: [0.89] Name collision dialog uses old name on renaming

Post by xnview »

See issue for current status and some details.
Pierre.
User avatar
xnview
Author of XnView
Posts: 43357
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: [0.89] Name collision dialog uses old name on renaming

Post by xnview »

This problem is supposed to be fixed in XnView MP 0.91. Please check and confirm the bug fix here.
Pierre.
Post Reply