Roland, > 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.
Not really. Today the interface has only 2 buttons. One to set in cache and one to reset it. The sync is not part of the interface, the goal is to do whatever is needed for the user to not have to care for this. > 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 ;-) :) Not really, see above. We already have reset the local copy. I plan to use this action to sync at the same time. 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 ------------------------------------------------------------------------------ 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
