🚀 go-pugleaf

Tommy wrote:

>i could find the error yet. i set startime with this code:
>
>GetSystemTimeAsFileTime(&StartTime.ft);

Well, as long as you have that problem, your next reported problem
will happen too, caused by the fluctuating elapsed time.

Nail down the StartTime changing problem first.  The rest will become
more clear.

>As i said the the time which is already need till the process is finished
>works fine. but there is one small thing i do not like. the time differents
>fluctuates very much. so my application shows that the process will be ready
>in 5 minutes, but one seconds later in takes 5 hours. this depends on if
>there are many small files copying at the moment or larger files.
>
>is there perhabs any better way to calculate the time which is still need
>without these large time fluctuations. when i copy completly large folder
>under windows the information how long the process still needs does not show
>such much fluctuations. so there should be a better way.

Once you get you elapsed time problem fixed, if it still changes too
much, you could go into higher mathematics, and practice curve
smoothing.  You'll probably need a good book on statistical methods to
figure that one out.

The reason you don't see MS's time jumping around, is, first, they
wait quite a while before displaying the first approximation. so they
have quite a bit of history to extrapolate from. Second, they don't
give very accurate figures.  Even then, if you watch a long copy, you
will see the figures change up and down.  I've seen it finish copying
with still "10 minutes remaining".