On Wed, 18 Sep 2013 13:38:55 Tobias Ellinghaus opined: > Let me try to put an end to this discussion by telling you the reason why we > removed the feature. > > In general it worked as intended and people were happy. Some might have > deleted their images accidentally, but that wasn't our concern. As you said, > users make dumb things and it's not up to us to protect them from free > choices. > > However, there were occasions where files were not copied over correctly (full > hard disk, gphoto2 problems, flaky usb connection, you name it) and darktable > didn't recognize that and subsequently deleted the original files. A few people > could restore them, others didn't notice until it was too late. Since adding > safety nets to find out that the copy process wasn't successful is more work > than we are willing to invest we decided to leave this part to dedicated tools > like this rapid-forgotthename thing. > > If you really want that feature back (and promise not to complain if anything > goes wrong) there should be the compile option "-DUSE_CAMERA_IMPORT=On" for > cmake. I don't know if that is still available, but it should. > > I hope I made some things clear. It wasn't about taking choice away from the > users but to protect them from unmaintained and possibly dangerous code.
Just a suggestion, but maybe a note in the documentation may help to explain this to users so that issue is not raised again. ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
