Le 19/08/2013 16:16, Jose Carlos Garcia Sogo a écrit : > While it seems to be a short term solution, I am not sure it is the > way to go. IMHO an internal flag in the db should be used, and every > image in the cache that is not matching the db status should be > discarded periodically. The problem I see with the tag is that tags > are written to the XMP files, so I can import a file with a XMP > telling that it has a local copy while it is not true. > > What do you think?
We've discussed this on irc and it was found ok to go this route. We already have a flag in the db and this is used to display the white color label to show files with local copies. But it is not possible to select based on this color label. At the same time dt has darktable|exported, darktable|changed... It seemed quite natural to add darktable|local-copy and this way user can select all pictures with local copies easily. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
