🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
>"Bob Gonder"  wrote in message
>
>> Before uploading, you get the file size from the operating system.
>
>You do not need to do that for uploads.  TIdFTP already knows the size
>of the file it is uploading, and provides that in the AWorkCountMax
>parameter of the OnWorkBegin event.

But you still need to remember it yourself, right?
OP was saying the value persisted (as a property?) in the old library.

>> In the OnWork() member, you add each AWorkCount to your running
>total
>
>That is not correct.  AWorkCount is already the total running count.
>Use it as-is.

Ok then the BDS2006 documentation is incorrect

AWorkCount	Number of bytes affected by the event

This is inside the OnWork Event, so the number of bytes per event seems to be the meanng
as prior bytes (and their events) are not affected by this particular event.

AWorkCount indicates the number of bytes sent or received in the read or write operation

Should have the word "Total" in there somewhere.

If you've already fixed the docs, it might be nice if CG hotfixed our help docs.

Feature Suggestion:
OnWork supply similar data as CopyProgressRoutine does for CopyFileEx.
(I realize I'm over a year late on that, but it just came up)
That's quite a bit of work too, I'd imagine as everything seems to go through OnWork
Maybe version11....