[GH-ISSUE #379] File transfer: File size and estimate download time / pause and resume #176

New issue

Closed

opened 2026-02-27 15:49:13 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 15:49:13 +03:00

Owner

Originally created by @webiummedia on GitHub (Sep 9, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/379

In the transfer window, please add the file size and estimate download time. Also adding a pause and resume would be a great feature. When a list of files is added to the download window, would it be possible to save the status in case quasar is closed or lost of connection and automatically resume on the next connection?

Originally created by @webiummedia on GitHub (Sep 9, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/379 In the transfer window, please add the file size and estimate download time. Also adding a pause and resume would be a great feature. When a list of files is added to the download window, would it be possible to save the status in case quasar is closed or lost of connection and automatically resume on the next connection?

kerem

2026-02-27 15:49:13 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-27 15:49:13 +03:00

Author

Owner

@webiummedia commented on GitHub (Sep 9, 2015):

I just confirmed that the file manager does not save the progress or even the list of files to be downloaded when we lose connection. Everything is emptied no resume at the moment. You need to rebuild the queue list.

@webiummedia commented on GitHub (Sep 9, 2015): I just confirmed that the file manager does not save the progress or even the list of files to be downloaded when we lose connection. Everything is emptied no resume at the moment. You need to rebuild the queue list.

kerem commented

2026-02-27 15:49:13 +03:00

Author

Owner

@yankejustin commented on GitHub (Sep 9, 2015):

I agree about this suggestion. Especially in the case where a block isn't correctly sent and ruins the whole progress of a potentially large file. :(

@yankejustin commented on GitHub (Sep 9, 2015): I agree about this suggestion. Especially in the case where a block isn't correctly sent and ruins the whole progress of a potentially large file. :(

kerem commented

2026-02-27 15:49:13 +03:00

Author

Owner

@ghost commented on GitHub (Sep 9, 2015):

This could be implemented easily and would be a nice addition

@ghost commented on GitHub (Sep 9, 2015): This could be implemented easily and would be a nice addition

kerem commented

2026-02-27 15:49:13 +03:00

Author

Owner

@MaxXor commented on GitHub (Sep 10, 2015):