On Tue, Jun 25, 2013 at 7:06 AM, Pascal Obry <[email protected]> wrote:

>
> Johannes,
>
> > there were repeated complaints about data loss (move files from cf card
> > via gphoto, have the `delete after import' aka `shoot me in the foot'
> > option checked). mostly this is due to some portion of user error (disk
> > full, check this option in the first place) or sudden disconnect from
> > gphoto. possible that our code could be improved here, but that part
> > isn't actively maintained. so it seemed the safest option to disable it
> > for the time being.
>
> I've never run into this issue!
>

me neither. but i'm not using the gphoto import, but use the regular
`import' button to import my mass-storage mounted cf-card and then use the
`copy' or `move' buttons in the right panel to split up my files into their
final folders. this works more reliable, faster (no ptp), and i can look at
the thumbnails in regular lighttable mode already.

arguably it would be good to spend some time fixing the old import module
for those who prefer it that way. let's see if someone steps up for this.

j.


>
> And BTW, it is a big USER mistake to ask for a *move* instead of a
> *copy*. That's a basic principle in photo editing. Until you have not
> put the RAW into a safe place it is far better to keep the data into the
> memory card. I have a set of card and format a card only when the
> pictures are on my RAID hard drive and often copied into an external
> (web service) storage.
>
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to