Operation "Move to" opens wrong dialogue

[josedumoretzsohn]

After selecting a few images, and commanding "Create Shortcut", the usual dialogue appears with the Folders to be reached. However, after clicking on the destination folder, a "strange" second dialogue appears asking whether I want to overwrite the images, one or all. This second dialogue is unnecessary, because the images moved are entirely new to the destination folder.

[xnview]

could you describe the way to reproduce?

[m.Th.]

1. Can you give screenshots + steps?
2. If you change the destination folder (for ex. make a new one), the problem persists?
3. What versions XnV MP/OS do you have?

[josedumoretzsohn]

could you describe the way to reproduce?

I did not understand your question? The bug is precisely the "opening of this second dialogue" (Replace/With: that usually only opens when there is/are image/images to be replaced), because the destination folder is empty, there is nothing to be replaced there.

[josedumoretzsohn]

1. Can you give screenshots + steps?
2. If you change the destination folder (for ex. make a new one), the problem persists?
3. What versions XnV MP/OS do you have?

Describing:
My version is XNView MP 0.89.
Steps:
1) In my Folder \zzCAPTURE\ there are 4 images, and I will create shortcuts to \zzEDIT\, which is empty
2) I select the 4 images, right-click on Create Shortcut. The shortcuts are printed on the \CAPTURE\ folder.
3) I select the shortcuts and command "Move To", either on its icon or typing ALT+M. The regular MOVE TO dialogue opens.
4) When II select the destination folder \EDIT, which is empty, the REPLACE/WITH dialogue opens.
5) The opening of the REPLACE/WITH dialogue is the bug itself, because the destionation folder is empty.

I can send screenshots; in fact, I created them, but don't know how to send them. I tried to, clicking on the IMG button above the Text Box, but it did not open my Folder Manager.

[josedumoretzsohn]

Just to add: if I OK the second (buggy) dialogue, the operation of MOVE TO (or COPY TO) succeeds; If I CANCEL this dialogue, the images stay where they are.

1. Can you give screenshots + steps?
2. If you change the destination folder (for ex. make a new one), the problem persists?
3. What versions XnV MP/OS do you have?

Describing:
My version is XNView MP 0.89.
Steps:
1) In my Folder \zzCAPTURE\ there are 4 images, and I will create shortcuts to \zzEDIT\, which is empty
2) I select the 4 images, right-click on Create Shortcut. The shortcuts are printed on the \CAPTURE\ folder.
3) I select the shortcuts and command "Move To", either on its icon or typing ALT+M. The regular MOVE TO dialogue opens.
4) When II select the destination folder \EDIT, which is empty, the REPLACE/WITH dialogue opens.
5) The opening of the REPLACE/WITH dialogue is the bug itself, because the destionation folder is empty.

I can send screenshots; in fact, I created them, but don't know how to send them. I tried to, clicking on the IMG button above the Text Box, but it did not open my Folder Manager.

[XnTriq]

I can send screenshots; in fact, I created them, but don't know how to send them. I tried to, clicking on the IMG button above the Text Box, but it did not open my Folder Manager.

Please refer to cday's tutorial on how to add attachments to a post.

[josedumoretzsohn]

The screenshots follow:
1) 01-Destinatio Folder Empty.jpg
2) 01_SourceFolder.jpg
3) 02-Selection-to-Create-Shortcut.jpg
4) 03-Create-Shortcut.jpg
5) 04-MoveTo-Icon.jpg
6) 05-MoveTo-Dialogue.jpg
7) 06-Replace-With-Dialogue-Opens.jpg

07-Replace-With-Dialogue-Opens.jpg

I can send screenshots; in fact, I created them, but don't know how to send them. I tried to, clicking on the IMG button above the Text Box, but it did not open my Folder Manager.

Please refer to cday's tutorial on how to add attachments to a post.

[josedumoretzsohn]

I tentatively installed the 0.90 .zip version, but the bug persists.

[xnview]

See issue for current status and some details.

[xnview]

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