Closed vatterspun closed 7 years ago
Certainly it is not smart to interrupt processing every time an error occurs. It seems to keep working smoothly, leaving files that can not be processed and continuing processing. But It is necessary to change how to display error messages. I’ll consider it.
The current interface is simple and I think that's a real asset. Additions that aren't really necessary might not make sense. I debated posting this for some time so if it doesn't make sense to add, that's fine.
I've given this some thought and I don't think it makes sense to add to the main interface. I can imagine it being added to an advanced options menu in the future, but I just can't shake the idea that this makes a wonderfully simple security program too complex. Closing the issue.
I'm not sure this is a good idea or not, but when protecting files with a password, it might make sense to keep protecting files and leave the unprocessed files as a list.
This could be solved with a manual describing the "Clear" process:
... or with the following feature:
Current behavior
When password-protecting a list of files, the program will stop if it encounters an error, the process freezes on that file (as below):
Requested capability
Ability to continue processing files.
Interface suggestion
A checkbox at the bottom of the window that is checked by default labeled "Stop on error" or unchecked for "continue processing on error". See rough mockup below: