Bug 154135 - konqueror/dolphin "pause" and "log" buttons on file transfrers
Summary: konqueror/dolphin "pause" and "log" buttons on file transfrers
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-15 20:11 UTC by usrrgt
Modified: 2024-09-14 16:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description usrrgt 2007-12-15 20:11:11 UTC
Version:            (using KDE KDE 3.97.0)
Installed from:    Ubuntu Packages
OS:                Linux

When I am copying files, sometimes is necessary  a pause button to continue the copy later (because the hard disk is very slow in these moment for other tasks).

And, too, a button to export to a TXT log the copied/uncopied files (for when a file is corrupted and is not posible copy. To know later that files have been copied and which not, for example, from CD/DVD to hard disk file transfers).
Comment 1 Pino Toscano 2007-12-15 20:18:35 UTC
> When I am copying files, sometimes is necessary  a pause button to continue the copy later

Isn't there a "pause" button in every progress dialog already?
Comment 2 usrrgt 2007-12-24 03:05:33 UTC
"Isn't there a "pause" button in every progress dialog already? "

At this moment I am not sure, but "export button" is not exists.
Comment 3 usrrgt 2007-12-24 03:07:24 UTC
But I sure that in KDE 3 these buttons are not exits.
Comment 4 usrrgt 2008-01-30 02:25:01 UTC
I try KDE 4.0.0 and I can confirm that these two buttons are not exits.
Comment 5 Christoph Cullmann 2024-09-14 16:18:04 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann