I'm getting caught out again by shotwell thinking it knows best.
I rename image files based on their tags as I find it very useful in
terms of portability and it is often useful in finding images very
quickly (using 'locate') without the need to fire up a photo package. (
http://www.bluecedar.org.uk/?p=143 ). f-spot allows a 'real' delete
(shift-delete) whereas in Shotwell I think it's a two-way process. Move
to Wastebasket - then move to desktop wastbasket.
So to rename images that I have tagged in shotwell (or f-spot), I would
export the files to a directory, then delete (move to wastebasket) the
files in shotwell. After renaming them outside shotwell, I then
re-import them, selecting 'Copy' rather than 'import in place'. But I've
only just discovered that shotwell hasn't been doing what I expected. In
fact, I'm not clear exactly what it has been doing. It obviously knows
I'm up to something as the log file shows it recognises the import as a
duplicate, with messages such as:
L 11880 2011-09-27 11:02:24 [DBG] BatchImport.vala:848: duplicate
photo detected, not importing /images/2011/09/24/24-September-2011 -
Durham Parkrun - Durham Parkrun - run7 - Parkrun -- (United Kingdom -
England - Elvet ED - Shincliffe) -- Sat 24 Sep 2011 09-04-12 BST.jpg
or sometimes more alarmingly as:
L 11880 2011-09-27 11:04:22 [DBG] BatchImport.vala:809: duplicate
linked photo found in trash, untrashing and removing transforms for
/home/dougie/renamejpegsout/24-September-2011 - Durham Parkrun - run7 --
(United Kingdom - England - Elvet ED - Durham) -- Sat 24 Sep 2011
09-18-05 BST.jpg
when the import is complete, and I use 'show in file manager' to look at
the imported files, I can see that it has not been copied to the /images
directory, but is still in place in /home/dougie/renamejpegsout. As I
delete this directory once I've imported the images this is a bit
dangerous for me.
I presume I can get around this by physically deleting the images from
shotwell before re-importing, but I do feel a bit uneasy as I've come
unstuck a few times now (e.g. no empty tags, quietly writing metadata to
image files even though write unchecked) where shotwell makes
assumptions about what to do without letting me know, unless I keep an
eagle eye on the log file.
I've checked the bugs and think this might be related to
http://redmine.yorba.org/issues/3687 ? Although in my case I haven't
noticed any performance issues.
Dougie
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
