You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we update the progress bar during a zip archive extraction only after a complete file has been fully extracted. This leads to visible jumps in the progress bar which does not look really smooth to the user.
Operation with a loop that manually copies the file content byte block for byte block. This allows us to update the progress bar more often to give the user a more smooth feeling.
Here an example how a byte stream can be manually copied in byte blocks (copied from #2064 (comment)):
Notes:
I'm not sure if counter contains the number of compressed or uncompressed bytes...
Additionally the input stream wouldn't be of type FileInputStream. Instead it would be of whatever type apache-compress gives us
The text was updated successfully, but these errors were encountered:
Currently we update the progress bar during a zip archive extraction only after a complete file has been fully extracted. This leads to visible jumps in the progress bar which does not look really smooth to the user.
To improve on this we can replace the current
Operation with a loop that manually copies the file content byte block for byte block. This allows us to update the progress bar more often to give the user a more smooth feeling.
Here an example how a byte stream can be manually copied in byte blocks (copied from #2064 (comment)):
Notes:
I'm not sure if
counter
contains the number of compressed or uncompressed bytes...Additionally the input stream wouldn't be of type
FileInputStream
. Instead it would be of whatever typeapache-compress
gives usThe text was updated successfully, but these errors were encountered: