(*** This bug was imported into bugs.kde.org ***) Package: konqueror Version: 3.0.1 (using KDE 3.0.1 ) Severity: wishlist Installed from: Mandrake RPMs Compiler: Not Specified OS: Linux OS/Compiler notes: Mandrake 8.2 I have this one complaint about copying and moving in a Konqueror. This problem happens with Windows too. I need to copy/move a SINGLE directory (with subfolders and files) from source A to target B. Sometimes when I'm in a rush I tend to copy/move right away WITHOUT CHECKING if target B has sufficient space to hold the files from source A. What Konqueror does is copy/move the files FIRST from source A then INFORM me LATER with a dialog box that there is no more space left on target B. After dismissing the insufficient space dialog box target B has the subfolders/files that were copied/moved first. Source A also has the remaining subfolders/files that were left out. This leaves me with TWO SEPARATE directories on source A and target B from the original SINGLE directory that I had in source A. Note that this will also happen if the copying/moving was interrupted by a power failure computer breakdown etc... It would be better if: 1. Konqueror TELLS me FIRST with a dialog box that there is insufficient space in target B BEFORE copying the files. Having been informed as such I could free more space on target B then copy/move the directory again. Going back to the two orphan directories in source A and target B... How can I RECONCILE the two directories into a SINGLE directory AGAIN on target B? I can do this manually. Suppose there are 20+ or more subfolders in the original directory? I'll waste a great deal of time manually reconciling the subfolders in source A and target B. Konqueror has this dialog box with Overwrite and Autoskip options but I doubt whether it can correctly recreate the original directory structure in source A. I suggest that: 1. Konqueror TAKES NOTE (writes to a temp file or something) of the directory structure BEFORE COPYING 2. IF the moving/copying process is INTERRUPTED by a power outage a computer breakdown or an insufficient disk space error Konqueror REMEMBERS the directories/files that were transferred to target B and those that were left on source A. 3. After I log-in again (or after I free-up space on target B) Konqueror will PROMPT me to RESUME the interrupted copying/moving AND correctly BUILDS UP the SINGLE DIRECTORY again in target B. I hope I put the problem across correctly. Michael (Submitted via bugs.kde.org)
Konqueror 3.0.2 CVS has a "Undo" in the right click menu.or the standard <Ctrl> Z. This should address the second part of the problem.. -- JRT
On Sunday 14 July 2002 12:22 pm James Richard Tyrer wrote: > Konqueror 3.0.2 CVS has a "Undo" in the right click menu.or the > standard <Ctrl> Z. > > This should address the second part of the problem.. Thanks James! That was quick! Michael
On Sunday 14 July 2002 12:22 pm James Richard Tyrer wrote: > Konqueror 3.0.2 CVS has a "Undo" in the right click menu.or the > standard <Ctrl> Z. > > This should address the second part of the problem.. Another usability suggestion: Can we elaborate more with "Undo"? Instead of merely prompting "Undo" it w= ill=20 be more helpful if we change it to "Undo Move" or "Undo Copy" depending on= =20 the interrupted action. Thank you very much. Michael
> Instead of merely prompting "Undo" it will be more helpful if we change it to "Undo Move" or "Undo Copy" This has been this way for a long time already. But of course the main problems remain: detection of out-of-disk-space case before hand, and easier way to resume the copy - although IIRC there's another report for the latter.
Is this still relevant or applicable with KDE Frameworks 5.45?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!