Hi all, First of all --- thanks you all for the 1.6 release. I think DT is a great piece of SW!
On 2014-12-14 03:13, Markus Jung wrote: > > The XMP files are supposed to be only a backup of the internal > database. > Until darktable 1.6, the sidecars had to be loaded manually if > something > changed, dt itself did not detect any changes but simply overwrite them > after opening the image in darkroom. > Really? I thought that .xmp had precedence if newer! In that case, this could be the biggest problem (together with the lack of undo) that DT still has, at least as a default. The problem is that I think a lot of people works with more than one PC, with a shared photo collection (I have one synchronized between various computers and laptops for safety). My expected behavior is that if the .xmp is newer, it is used before the database --- that is, the internal database should be just a high speed cache for the photo collection. That would make the multi-machine work automatically, and even make DT compatible in the workflow with, for example, digiKam or other SW that can be instructed to look at sidecars first. > Since dt 1.6, there is an option "Scan for changed XMP files on > startup", which would have avoided your problems. So now with this option the behavior is like the described above? This is great! Romano ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
