Fab's AutoBackup forums

Welcome to Fab's AutoBackup technical support forums
Bienvenue sur les forums de support technique de Fab's AutoBackup

You are not logged in.

Announcement


Due to a large amount of fake accounts registrations for advertising purpose (spam), this forum does not accept new registrations any longer.
You can still browse existing threads to find the help you are looking for. If you do not find it and have questions, please use this contact form.

====================================

En raison d'un nombre important d'enregistrements de faux comptes utilisateurs à des fins de spam (publicité non sollicitée), il n'est désormais plus possible de s'enregistrer sur les forums de support technique.
Vous pouvez toujours parcourir les sujets existants pour trouver ce que vous recherchez. Si vous ne trouvez pas l'information et avez des questions, veuillez utiliser ce formulaire de contact.

#1 2017-01-31 09:24:27

berkayict
Member
Registered: 2014-06-03
Posts: 16

[SOLVED] Feature request: Time remaining

Dear Fab,

Is it possible for you to implement a time remaining field in the progress window?

Offline

#2 2017-01-31 09:33:19

Fab
Administrator
Registered: 2011-05-11
Posts: 1,307

Re: [SOLVED] Feature request: Time remaining

This is something I can try but this is not a really reliable information as transfer rates change all the time.


Fab

Offline

#3 2017-01-31 09:38:22

berkayict
Member
Registered: 2014-06-03
Posts: 16

Re: [SOLVED] Feature request: Time remaining

Yes, I don't expect it to be very reliable, but it would be nice to get a global estimate.

You could try giving an estimate calculated by an avarage speed instead of the current speed.
Or maybe there are other more reliable methods.

Thanks in advance, this will be a great addition to your near perfect product!
Keep up the good work!

Offline

#4 2017-01-31 09:42:42

Fab
Administrator
Registered: 2011-05-11
Posts: 1,307

Re: [SOLVED] Feature request: Time remaining

In my opinion, using current speed should result in more accurate results. I prefer going this way in a first place.


Fab

Offline

#5 2017-01-31 09:48:38

berkayict
Member
Registered: 2014-06-03
Posts: 16

Re: [SOLVED] Feature request: Time remaining

Sure thing! You're the developer, do it the way you prefer!

Offline

#6 2017-01-31 13:40:47

Fab
Administrator
Registered: 2011-05-11
Posts: 1,307

Re: [SOLVED] Feature request: Time remaining

So far, results are not that good. It generates more headaches than anything else. I guess I under estimated the thing


Fab

Offline

#7 2017-01-31 13:54:20

berkayict
Member
Registered: 2014-06-03
Posts: 16

Re: [SOLVED] Feature request: Time remaining

I already feared that.

I have implemented this function in a web application myself.
Althought I can imagine it might be a lot different to your application, this is how I did it:

Calculated the speed during 10 seconds.
Took the average speed during that time.
Calculate the estimated time.
Updated the estimated time once per 10 seconds.

Offline

#8 2017-02-22 14:03:32

Fab
Administrator
Registered: 2011-05-11
Posts: 1,307

Re: [SOLVED] Feature request: Time remaining

Hi,

I am sorry but this is generating more problems than anything. The fact is that there are 2 parts of the program that copy files and 2 others that moves them. The data copied can be monitored for only one of them (the one that sends feedback to the progress bar) but not the others, especially those designed for copy retries if the usual method fails. To make this easier, I should have designed the program a different way. I prefer stopping here and keep a program that works fine this way.
I hope that you will understand my point of view.


Fab

Offline

#9 2017-02-22 14:04:57

berkayict
Member
Registered: 2014-06-03
Posts: 16

Re: [SOLVED] Feature request: Time remaining

Hi,

Of course, thanks for your time spent investigating this!

Keep up the good work!

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.031 seconds, 7 queries executed - Memory usage: 517.02 KiB (Peak: 517.66 KiB) ]