In the meantime, I have to write the following code to correctly work with ZIP files:
Some callbacks are really needed.
This really belongs to the support requests tracker.
There is: check the general purpose flags. As per APPNOTE.TXT, bit 0 indicates that the file is encrypted.
What's that supposed to mean? You know the file size, you know your position, what else do you need to manage progress?
Well, whoever designed the extraction code should take care of that. As far as I'm concerned, I have only a few utility methods in JlCompress which indeed support no progress/cancellation/callbacks - but they aren't supposed to. If you need something more complicated, you have to do it yourself, QuaZIP only provides the necessary tools.
OK, it's indeed a good idea.
I don't see how that's any different from managing progress with any kind of QIODevice. QFile, for example.
The code in the link illustrates the way I manage progress during extraction
I had to modify the code of extractDir
JlCompress is just a simple utility class. I could improve it, but it's not the main purpose of QuaZIP. The class wouldn't even exist if it wasn't contributed by someone. QuaZIP is a lower level library than that. Its purpose is to provide QIODevice API and some really necessary methods to work with the ZIP structure.
Thanks a lot for the explanation!
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.