Am 14.12.2014 um 12:20 schrieb [email protected]: > 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.
No, the database has always been the primary (and only) location accessed during regular use. >> 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! Right. To quote the manual: ----------------------------------------------------------------------- look for updated xmp files on startup Check file modification times of all XMP files on startup to find out if any got updated in the meantime by some other software. If updated XMP files are found a menu opens for the user to decide which of the XMP files to be reloaded – replacing darktable's database entries by the XMP file contents – and which of the XMP files to be overwritten by darktable's database (default off). ----------------------------------------------------------------------- Regards, Markus ------------------------------------------------------------------------------ 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
