[Originally posted by pxstein on 2009-12-26 08:37:21-08]
I loaded a jpg picture in ExifToolGUI (under WinXP).
Then I selected the menu
Modify->Remove Metadata...
Finally I clicked "All Metadata" (with or without "-backup")
and the button EXECUTE.
Then I got an error popup
"List index out of bounds (0)"
When I does the same approx 20 minutes later again it all works.
However this seems to be a bug.
If there is a lock on this picture file then ExifToolGUI should tell it the user.
I suggest to fix this in the next release
Thank you
Peter
[Originally posted by bogdan on 2009-12-27 10:52:48-08]
Hi Peter,
Right now I've uploaded new GUI version, where I've a little changed error handling in GUI -which should help you, I hope, to findout why (sometimes) it doesn't work as expected.
Greetings,
Bogdan
[Originally posted by exiftool on 2009-12-27 12:21:01-08]
Hi Bogdan,
It sounds like the error occurred because the picture file was being
used by another application (ie. locked when exiftool tried to write
it). Could this cause the problem that was observed?
- Phil
[Originally posted by bogdan on 2009-12-27 14:31:42-08]
Hi Phil,
To be honest, it's actually my fault since beginning of making GUI: for most of the time, I've simply assumed commands sent toward Exiftool will be executed "as expected". As a result (of that thinking), GUI didn't fully checked (and parsed) resulting messages from Exiftool. Much later (now?), I "discovered", "assumming" isn't enough.
I know in what cases such message (List index out of bounds) inside GUI can appear: it's when GUI expect (thus, automatically reads) "out" message (lines) from Exiftool, but there isn't any (there might be some "error" message from Exiftool, though). By trying to read nonexistent (result) message from Exiftool, GUI displays "List index..." message -which is actually GUI's internal error handling (thus user shouldn't see it at all).
What can I do? I can't force Exiftool to do something impossible (like modifying locked file or preventing some backup software by restoring files in previous state, etc.).
What I did is, GUI now reads and shows all messages which Exiftool writes after execution -but only if they exist! Now user (as Peter suggested) can see the reason of error (as Exiftool displays it) and look after solution by himself.
I only hope this was the solution... as there are so many possibilities one can't predict.
Thank you for jumping in.
Bogdan