[ros-bugs] [Bug 5176] shell: Copy/Paste failure when multiple files are selected at once.

[ReactOS.Bugzilla at reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=5176





--- Comment #12 from BrentNewland <brent.newland at gmail.com>  2012-04-08 03:11:34 CET ---
Here is an IRC transcript which might give a bit more information.

The bug still exists in latest builds.

[21:39:46] <BrentNewland> http://www.reactos.org/bugzilla/show_bug.cgi?id=5176
[21:40:07] <BrentNewland> I believe the source of this bug would be in
http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/kernel32/client/file/
[21:40:17] <BrentNewland> possibly move.c, copy.c, or dir.c
[21:40:25] <BrentNewland> This bug affects both files and folders
[21:42:45] <BrentNewland> Essentially, when moving or copying multiple folders
(I don't think it happens with just one folder) with or without files inside,
to a folder that contains a folder that matches the name of one of the folders
being copied (possibly just the first folder being copied, alphabetically), the
folders will not be moved to their destination folder, but instead inside of
the folder that has the same name
[21:42:57] <BrentNewland> as the first folder.
[21:44:13] <BrentNewland> For example: copying the folders c:\test\inf and
c:\test\other (by highlighting both in explorer and choosing copy) to
c:\reactos (by entering the folder, right clicking, and pasting)
[21:44:49] <BrentNewland> will result to c:\test\inf and c:\test\other both
being copied to c:\reactos\inf (e.g. c:\reactos\inf\inf c:\reactos\inf\other)
[21:45:39] <BrentNewland> attempting to rename either of those folders while
they are inside of that parent folder will cause the folder to disappear (e.g.
rename c:\reactos\inf\inf to c:\reactos\inf\inf2 will make that folder
disappear)
[21:47:35] <BrentNewland> I have tested ReactOS explorer in Windows 7 and it
used the Windows file copy functions, and everything worked fine.


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.