Bug 210857 - Option to enqueue copying of files while a copy is already in progress
Summary: Option to enqueue copying of files while a copy is already in progress
Status: RESOLVED DUPLICATE of bug 161017
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.3
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-17 06:40 UTC by marrammar
Modified: 2012-11-23 15:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description marrammar 2009-10-17 06:40:12 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Ubuntu Packages

Often while in the process of copying large files or folders from one drive to another I realize that I need to copy yet more files from the same source to the same destination.  Currently I can drag and drop those additional files from source to destination and initiate a second copy operation so that two copy operations are happening simultaneously.  This slows things down considerably.  Sometimes it is best to wait until the first operation is finished before initiating the second but that also means waiting around for the first operation to finish.  Neither option is ideal.

Would it be possible for Dolphin to recognize that a copy operation is already in progress and to offer an option to enqueue the second copy operation to improve overall throughput?  If that's possible, after dragging and dropping the second file/folder to the destination maybe it could pop up a dialog asking if you wish to enqueue the second copy.  Maybe then the second copy operation could show up in the notification area in the system tray as "queued"?  Thanks.
Comment 1 Patrick 2010-04-11 16:41:41 UTC
duplicate of Bug 161017 (but can't mark it as such)
Comment 2 Frank Reininghaus 2012-11-23 15:23:23 UTC

*** This bug has been marked as a duplicate of bug 161017 ***