| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
If the storage is fast enough, passing a bool to updateCopying does not
suffice. Then the SIGNAL with inProgress == true could arrive *after* the
work is already done, leaving the copy indicator in an inconsitent
state.
So check the QThread directly by ->isRunning() instead of passing a
bool.
|
| | |
|
| |
|
|
|
| |
Add a new label to the statusBar: When it's green the FileCopier is
idle, when working, show the count.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hmm, as it turns out QFile does a much better, e.g. faster, job than my
open-coded file copy with a progress dialog.
I always wondered why it only did 150-170Mbit. I thought that it was
just the calculation, but now I have 400 Mbit, and it still stalls at
150 Mbit.
QFile::copy maxes out the line, so get rid of the ProgressDialog and
show a status message instead.
Copy can be canceled by the context menu, but FileCopier will always
finish the current file, because I don't want to lock and unlock the
CancelMutex during copy. Besides, QFile::copy doesn't admit that :)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This endeavor started out quite innocently: fix the connect syntax in
ProgressDialog, but it quickly became much more. Vom Höxchen aufs
Stöxchen :)
First I thought it would be nice to add a total count to the
ProgressDialog. Then I realized that I had QElapsedTimer::restart()
totally wrong. It returns the ms *since the last restart*! It doesn't
reset to zero, so fix that.
While testing that I noticed that the download speed was quite below
average, so change the buffer size and only check if we were cancelled
when the timer elapsed. But that wasn't it. Eventually I dug into my
firewall rules and routings to get it right.
|
| |
|
|
|
| |
Show how many files we have, and display the transfer rate in Megabytes
per second. Can't believe that it worked right from the start :)
|
| |
|
|
| |
Elide the text if necessary. Only show the destination directory.
|
|
|
Create a FileCopier and show a custom, non-modal progress dialog when
we're copying files.
Turns out that a QProgressDialog always shows when it's created. This is
by design, so I had to implement one that fits my needs.
Also, a buffer size of 32K (as used in MKVMerger) is way too small to
max out the available bandwidth, so I set it to an (arbitrary) value of
16MB.
|
