---- Reported by shotwell-maint@gnome.bugs 2010-06-15 07:17:00 -0700 ----

Original Redmine bug id: 2114
Original URL: http://redmine.yorba.org/issues/2114
Searchable id: yorba-bug-2114
Original author: Maarten de Boer
Original description:

When importing it scans all the underlying folders as well which I don't want
with the folder system I'm using. It would be nice to have an option either in
the import dialog or the preferences dialog to enable/disable the recursive
import behavior.



---- Additional Comments From shotwell-maint@gnome.bugs 2010-10-27 07:05:00 -0700 ----

### History

####

#1

Updated by Adam Dingle over 3 years ago

  * **Priority** deleted (<strike>_High_</strike>)

Thanks for the suggestion. Dropping to medium since this won't make 0.6.

####

#2

Updated by Maarten de Boer over 3 years ago

Ok, well I'm not in a hurry any more, modified the SVN version to include a
gconf entry to enable/disable this behavior and modified the code to handle
it. I'm willing to post a patch so it can be included in the SVN version and
even possibly 0.6?

What I also noticed when I was browsing through gconf is that there is no
option to turn off automatic copying to the photos folder while importing, you
have to manually untick the checkbox every time you import.

The only way I was able to change that behavior was to change source code,
should I post a separate ticket?

####

#3

Updated by Adam Dingle over 3 years ago

nan0meter,

I'm glad you can hack the code to make it work the way you want to. :)

I think we'd rather not take the non-recursive change so late in the 0.6
cycle, especially since you are the only person we know of who wants it. The
way importing works may change significantly in 0.7 anyway, so I'd rather
consider this change as part of the 0.7 cycle. I think we'll be having some
0.7 planning discussions on the mailing list and we could mention this
potential feature there as well.

By the way, you can't simply use Nautilus to navigate to the folder you want,
select all the photos there and simply drag them in? Or is that too awkward?

Regarding your second question about turning off automatic copying: this is
about to change in 0.6 anyway. See #1602 for a detailed description about how
importing will now work. When you import using File->Import From Folder, we'll
now explicitly ask you every time whether to link or copy. We're disinclined
to have a preference for this because we think that the link/copy distinction
is so important that the user should always be aware of it at the time they
perform the operation. If you always want to link, the easiest way is to
navigate to the folder in Nautilus and simply drag the files in. At the moment
you have to hold down Ctrl+Shift to link rather than copy, but once we commit
our changes for #1602 we'll link by default, at least when you're dragging
from the same filesystem that contains your library directory.

####

#4

Updated by Maarten de Boer over 3 years ago

  * **Status** changed from _Open_ to _5_
  * **Resolution** set to _fixed_
  * **% Done** set to _100_

Ah ok, looking forward to 0.6 and 0.7! I didn't know that I could drag stuff
in, which is easy to use as well although I was used to “import†with
other programs like f-spot and bibble.

Thanks for your quick support!

####

#5

Updated by Jim Nelson about 3 years ago

  * **Status** changed from _5_ to _4_
  * **Resolution** deleted (<strike>_fixed_</strike>)
  * **% Done** changed from _100_ to _0_

####

#6

Updated by Jim Nelson about 3 years ago

This has been requested by a user on Launchpad:
https://bugs.launchpad.net/ubuntu/source/shotwell/bug/667279



--- Bug imported by chaz@yorba.org 2013-11-25 21:45 UTC  ---

This bug was previously known as _bug_ 2114 at http://redmine.yorba.org/show_bug.cgi?id=2114

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution