On Sun, Oct 28, 2012 at 10:43 PM, Torsten Bronger <[email protected]> wrote: > Hallöchen! > > Pascal de Bruijn writes: > >> On Sun, Oct 28, 2012 at 9:29 PM, Torsten Bronger >> <[email protected]> wrote: >> >>> Pascal de Bruijn writes: >>> >>>> [...] >>>> >>>> I think this is by design. Darktable's primary source of >>>> information is it's database. We write the .xmp files for >>>> redundancy and easy interchangeability between Darktable users. >>> >>> What's the rationale of this precedence? I can imagine only use >>> cases when the user would like it the other way round. >> >> Speed for one I think. > > Comparing timestamps would be enough for all practical purposes.
Timestamps aren't reliable per-se... At least now the precedence is simple to understand, more logic means it's harder to grasp, and more risk of unexpected behavior. >> Darktable is an image management solution, it's assumed you manage >> your library using Darktable, and don't fiddle around with the >> files behind Darktable's back. > > But consider these two situations: Restoring RAW/xmp from backup; > copying RAW/xmp from main computer to laptop for editing further and > then copying back. Then you need to drop the images from your library and re-import them. Regards, Pascal de Bruijn ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
