After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 325687 - Import only selected photos (not just folders)
Import only selected photos (not just folders)
Status: RESOLVED WONTFIX
Product: f-spot
Classification: Other
Component: General
CVS
Other All
: Normal enhancement
: ---
Assigned To: F-spot maintainers
F-spot maintainers
gnome[unmaintained]
: 338578 340777 477094 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-03 22:22 UTC by Jean-François Fortin Tam
Modified: 2018-07-12 00:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2006-01-03 22:22:44 UTC
Sometimes my "test user" wants to import only a part of the pictures I took. By
using the import dialog, she can only import all the pictures, and is forced to
remove the unneeded one by hand in the browser.

The easy solution would be to add "pre-checked" checkboxes besides each image on
the left of the import dialog. That way, you can uncheck anything, or select
multiple images, right click and uncheck them all at once.

An option to "automatically add new pictures added into the Photos folder" would
then be possible after that.

Other information:
Comment 1 Bengt Thuree 2006-02-20 06:01:07 UTC
I like this idea.

Add a checkbox to each photo, default to tagged.
Some extra buttons (Tag all photos, Un-Tag all photos, Tag selected photo)

Of course, the dual window thing (import window, and open folder window) makes it a bit tricky to have a clear import button though.
Comment 2 Bengt Thuree 2006-02-20 06:04:49 UTC
Forgot, this should be an enhancement bug
Comment 3 Gabriel Burt 2006-05-08 03:04:46 UTC
*** Bug 340777 has been marked as a duplicate of this bug. ***
Comment 4 Bengt Thuree 2006-05-18 02:54:03 UTC
*** Bug 338578 has been marked as a duplicate of this bug. ***
Comment 5 Bengt Thuree 2006-05-18 02:57:29 UTC
Changing title from "the import dialog needs to be able to only import partially"
Comment 6 nicklas boman 2006-06-07 22:00:51 UTC
wouldnt it be possible to have another option in the dropdown menu, that today has "select folder" and "<insert camera model here>", an option like "select photo" wich brought up a simple file-selection dialog where you got to choose one or more photos from a certain folder?
Comment 7 Jean-François Fortin Tam 2006-10-24 22:04:25 UTC
Oh and I forgot to mention, this bug obviously depends on one condition:

f-spot NOT starting all the import process before I click the "import" or "finish" button. I hate to see f-spot starting to load everything before I even made sure I wanted to import it. It may save 2-3 seconds, but it's not a good idea to import 3000 pictures without the user confirming it. Any chance of this being changed for the next release?
Comment 8 Jean-François Fortin Tam 2006-11-12 16:18:08 UTC
Could this get fixed for the next version? I really *can't* use f-spot at all because of this. 

Because I can't import single pictures by drag and drop without it *FORCING* me to create a ~/Photos folder (bug #374324), because I can't import the same folder and just hope it will import the new photos because it will create tons of duplicates (bug #169646?) and because it's just beyond hope to use this dialog with its current functionality in the 0.2.1 release :(

I really would like to use F-Spot, but I can't even use it as an art gallery manager because it *insists* on reorganizing my hard drive by force (bug #329040).
Comment 9 Floris Kruisselbrink 2006-11-16 12:51:23 UTC
The import interface as it is right now is rather confusing: you can in fact select some images to be imported, but when you click import suddenly you have all the files from that folder imported.

It's very annoying that it does not do what you told it to do (select some pictures, and import those), but it silently imports also the pictures you don't want, in my case usually because I already imported them a while ago!
Comment 10 Darin 2007-01-10 12:49:02 UTC
I am all for this request/fix. As Jeff said, it does depend on a few other aspects being fixed or changed. Right now importing is a  little confusing. When importing, a few questions ran through my head. Which photos are being imported, and where are they being imported to? - Also How do I easily delete the source images after they're imported? - But that may not be specific to this submission.

Jeff did mention a few of the same things I thought while using F-Spot. A way to avoid F-Spot forcing the creation of a ~/Photos folder is to allow the user to set a default Library Folder on first use, or afterwards in the preferences. It would also save a little confusion if, in the preferences, the user were allowed to choose whether files should be copied to chosen folder or not. Taken a step further, allow the user to choose whether source images should be deleted or not - a biggy for transferring from Digital Cameras. Not that these options should be removed from the Import dialog, but they should be the default selections, and if photos are dragged into the Library, it should use these default selections.

I guess maybe that is a seperate issue, but it was mentioned, so I thought I would add my thoughts.

Check Boxes next to images for easy selection (with select all and select none options), Destination folder defined by user, and Not importing until decisions are made and Import is clicked are three things I would love to see changed. As it is, it's a little confusing, I think, to experienced users... much less people still learning.

Thanks very much to everyone involved in this project! I really enjoy it so far, and I love the idea. It's the first piece of Photo Management software I've ever wanted to use! I can't wait to see it get even better! Thanks again!

- Darin
Comment 11 nicklas boman 2007-01-13 21:29:28 UTC
I have started to look at this a couple of times, more or less intense.
What usually happens is that i endup in confusion. Where, how...

Where should i look to do changes.
One could think that ImportCommand.cs would be the place. But it seems that its not the only place to look. Right?

How would this be implemented.

Where the Where is more concerning, than the how.
Comment 12 bill 2007-11-12 01:58:10 UTC
Is this being worked on?  F-spot is a none starter because of the import mess.
Comment 13 Maxxer 2007-11-25 11:52:59 UTC
*** Bug 477094 has been marked as a duplicate of this bug. ***
Comment 14 Frederik Elwert 2008-06-27 14:34:15 UTC
I would absolutely second this request. As Floris said, it's confusing that selecting images in the import dialog is possible, but has no effect at all. So either should only the selected photos be imported, or a solution like the proposed check boxes should be implemented.
Comment 15 crash 2009-06-11 17:08:55 UTC
This bug has been around for quite a while now. The issue I am having is that F-spot copies the files to my photo-folder before I imported them. Even if I only want to import a few of the photos, they were being copied anyway and I have to remove them by hand.

I would suggest to copy only the photos that have been selected for importing and copy them after clicking the Import-button.

What do the developers think of that?
Comment 16 Duncan Doyle 2010-03-20 18:45:08 UTC
I've got the same problem. F-Spot is getting better and better, but this bug is really anoying. Being able to select which images to import seems like a basic feature for a photo manager. I'm shooting 15MP images on a 8GB card. Everytime I want to import a couple of images, my whole card gets imported (yes, I use 'duplicate detection', but there are a lot of images on the card that I don't want to import on this machine).
Comment 17 André Klapper 2018-07-12 00:11:15 UTC
F-Spot has moved to https://github.com/f-spot/f-spot/issues

If this Bugzilla ticket is still valid in a recent version of F-Spot, please feel free to post this topic as a ticket in the F-Spot project on GitHub.

Closing this report as WONTFIX as part of Bugzilla Housekeeping as we are planning to shut down GNOME Bugzilla in favor of GNOME Gitlab.