Hi again, Am Mittwoch, 3. Juli 2013, 20:28:59 schrieb Pascal Obry: > We could have both but I would really prefer not having another button > for this.
I just think that the autosync-on-start wouldn't be very obvious for the user. In case he doesn't know and he wants to sync the images with the external storage but keep them cached afterwards, he would first have to uncache them and recache them afterwards. Under the assumption that the external storage is not very fast, this process would take a long time as all the raw files would be deleted and copied over again, instead of just writing a few hundreds of kilobytes worth of xmp files. > Right, this probably means that we want to forbid removing a local > cached image if it has been edited and the original file is not present. > When the original file is present we have the opportunity to sync back > the xmp just before purging the image from the cache. Thinking about it > this seems the safest option. Ok, so instead of a "remove" button we now have a "sync & remove" button. But to do a sync without a remove, we would have to restart darktable?? Sounds like we are getting closer to a "sync only" button ;-) No, just kidding. Thanks a lot for listening, Roland ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
