GNOME Bugzilla – Bug 549437
ctrl + drag & drop file duplication does not work in list view
Last modified: 2009-05-11 08:42:11 UTC
Please describe the problem: This is on Ubuntu Hardy. This is what *should* happen (it works in symbol view in nautilus or at the desktop): * Create a file, "foo.txt". * Drag it, then drop it to the same window while holding Ctrl (cursor changes to copy cursor). * A copy of the file, "foo (copy).txt" is created. This is what happens in list view: * The cursor changes to the copy cursor (plus sign) when Ctrl+dragging. * When you drop the file to the same window, nothing happens. * When you drop the file to the same folder open in another window, nothing happens. Steps to reproduce: Actual results: Expected results: Does this happen every time? Yes. Other information: Bug is also reported in Ubuntu launchpad: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/261108
I can confirm this issue is Gnome 2.24.1. Dragging and dropping using the middle mouse button also does not work. Ctrl+C Ctrl+V does work.
Created attachment 125460 [details] bug demonstration
Created attachment 127189 [details] [review] Patch The altered if-case in the patch used to prevent from dropping an item in the source folder for list-view in general. The new if-check prevents from dropping an item to the source folder just for move operations in list-view. Creating a copy or a link of the dragged item in the same folder is now permitted like in icon-view.
Patch works and looks fine to me. Would be nice to have a name to credit it to before we commit it though.
you can just use my nick "logari81", if you want
Setting patch status to reflect comment #4. It's anyway too late in the cycle now to commit this, so you should commit it after branching.
(In reply to comment #6) > Setting patch status to reflect comment #4. > It's anyway too late in the cycle now to commit this, so you should commit it > after branching. Now that nautilus has branched, can this please get committed to master?
Pushed this to master. Closing as FIXED. Thanks for the patch logari81.