I thought of a few more (hopefully simple!) enhancements that could be made to archive processing:
Even if DO doesn't include a list of passwords, perhaps it could remember the password entered by the user and continue to try that password if the user has selected several files to be extracted (thus saving the user from entering the password over and over and allowing the extraction process to proceed unattended).
This one is probably simple, but may be slightly difficult to explain. Let's say that I have the following files:
If I selected all of those files and tell DO to extract them, the process will begin to work as expected, but when DO gets to Album1.part2.rar it will generate an error because that file is not the first file in the archive set. The same will happen with the other .part2 and .part3 files. Thus, to avoid errors, a user needs to be careful to only select the .part1 file for extraction. So, I wonder if it would be possible for DO, when it encounters a .part2 (or .part3, .part4, etc.) to check whether it has already processed the associated .part1 as a part of that extraction process and, if so, not generate the error?
Thanks as always!