Performance: check for existing files *before* doing the processing on a picture
Bug #497594 reported by
Jeff Fortin Tam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Phatch |
Confirmed
|
Wishlist
|
Unassigned | ||
phatch (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: phatch
Currently, if you uncheck the "Overwrite existing images" option, phatch still processes the image before trying to check if it should be saved or not.
I know this is not easy to fix, but ideally, when I have a thousand images to process and launch the batch job multiple times, it should just continue where it left off, without reprocessing images that already have an existing output file.
Changed in phatch: | |
status: | Incomplete → Confirmed |
Changed in phatch (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in phatch: | |
milestone: | 0.2.7 → 0.2.8 |
summary: |
- performance: check for existing files *before* doing the processing on a + Performance: check for existing files *before* doing the processing on a picture |
Changed in phatch (Ubuntu): | |
importance: | Undecided → Wishlist |
To post a comment you must log in.
These are two different issues:
1) check for existing files *before* doing the processing on a picture
2) Resuming a session with (thousand) images
2 could be much more easy to fix. We could provide a "Tools>Resume Session" entry. This invokes a GUI where you can choose from previous unfinished sessions and have an overview of finished and unfinished images.
1 will be very hard if not impossible under certain conditions. It would only be possible if Phatch could ignore variable changes in the save action. For example if Phatch uses an imagemagick action it is impossible to know the new image dimensions, but also for autocrop etc ... As ignoring variable changes will lead to incorrect results and possibly harm the reputation of Phatch, I don't feel it is worth the effort.
What is your reaction?