Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Duplicate To for folders in the filesystem dock may cause unexpected behavior #81436

Closed
Rindbee opened this issue Sep 8, 2023 · 0 comments · Fixed by #81437
Closed

Comments

@Rindbee
Copy link
Contributor

Rindbee commented Sep 8, 2023

Godot version

v4.2.dev4.official [549fcce]

System information

Godot v4.2.dev4 - Linux Mint 21.2 (Victoria) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 Ti (nvidia; 535.86.05) - Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz (4 Threads)

Issue description

Select a folder A in the FileSystem dock, right-click to open the context menu, select Move/Duplicate To..., select another folder B in the popup dialog, and check Copy File(s) , click the Copy button to copy:

  1. if A is an empty directory, duplication has no effect.
  2. If B already contains A, trying the Keep Both option will result in a path like B/A (2)/A/.
Peek.2023-09-08.07-55.mp4

The second case above also applies to Move To.

Peek.2023-09-08.08-39.mp4

Steps to reproduce

See above.

Minimal reproduction project

N/A

@Rindbee Rindbee changed the title Using **duplicate to** for folders in the filesystem dock may cause unexpected behavior Using Duplicate To for folders in the filesystem dock may cause unexpected behavior Sep 8, 2023
@Rindbee Rindbee changed the title Using Duplicate To for folders in the filesystem dock may cause unexpected behavior Using Duplicate To for folders in the filesystem dock may cause unexpected behavior Sep 8, 2023
@akien-mga akien-mga added this to the 4.2 milestone Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants