Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Chilkat wrapper
Message
From
27/04/2021 04:14:37
 
 
To
27/04/2021 00:44:33
General information
Forum:
Visual FoxPro
Category:
Third party products
Title:
Miscellaneous
Thread ID:
01679872
Message ID:
01680028
Views:
48
>>the dfpug and vfx fll include the original zLib C code - and you have the option to tweak the GUI (which was neccessary, as on oodles of tiny files GUI slowed down processing a LOT).
>>
>>Changed that, added a property for updating GUI every x files processed.
>>Hollered long enough to include that into the release - having the source gives you such options and now you can either change or create a subclassed GUI with values set to your needs ;-)
>>
>>@Christian: If you decide to use Tores mail: Set it to every 20 files at least if not working ALWAYS with multi MB files - 20 is good for small dbf, still to small for .bat, png and small bmp. The C code will run at satisfying speeds ;-))
>>
>
>Thanks for the tip. Since teh VFPCompression started working again, and no other client had the same issue, I did not change that part. However for next time I would try using vfx.fll to see if I can build a wrapper for that one.
>

You already have a wrapper in form of the GUI which - at least in the vfx version for certain - is included in source.
This GUI in original form got a refresh on each file processed by the fll, updated to nnnn of xxxx files in upper right corner. IIRC it was a simple wrap of the screen update call by a if nnnn/thisform.nNewDivisor_by_TG=0.

>With 20 files you mean to iterate batches of 20 files each to add them to the same archive, or to add maximum 20 files to one archive and create multiple zip files?

Neither. Just NOT call the status update on each file zipped, but according to human perception values. For me such threshholds are in the 5s - 30s range, as the added time for screen update will be irrelevant and on a 1 minute runtime jumps in status bar of a few % every 5s are not taxing back brain calculation ALWAYS triggered ;-)

On longer running process it is only necessary to prove process was alive within last 30-90s and show current status: If your runtime is ~15min you have only 900s to look at the screen, updating on each of the xx.xxx files processed on small files is contraproductive ;-)

regards
thomas
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform