GNOME Bugzilla – Bug 452476
Importing New Images (via drag and drop) doesn't copy to the ~/Photos/ Folder
Last modified: 2009-08-11 13:31:04 UTC
Please describe the problem: Using 0.3.5 on Kubuntu Feisty. When I drag and drop and image onto the main F-Spot window, I expect it to copy the file into ~/Photos/... but it does not. It leaves the file where it is and imports it. If I then delete the file, it disappears from F-Spot. I can hold ctrl when I drag and drop and then it will copy the file. Steps to reproduce: 1. Open up a folder in Konqueror 2. Select a JPG image 3. Drag it onto F-Spot 4. Right click on the image after it imports and select "Copy Image Location" 5. Open a text editor and select "paste". Actual results: The directory pasted is the directory from step (1) above and not /home/dave/Photos/06/29/ or similar. The photo is imported into F-Spot but the image is not copied to ~/Photos/ Expected results: Older versions of F-Spot copied the image to ~/Photos/ by default and so I would expect this version to do the same. Does this happen every time? Yes. Other information: Inside my 'Preferences' tab I have 'write metadata to file' checked and I have the import folder set to ~/Photos/
Hi David, the default didn't changed in trunk... some usual additional questions to spot the bug: - does it work while dropping from nautilus ? - what does the mouse cursor looks like while dropping ?
From Nautilus: Dropping will copy it to ~/Photos everytime. Dropping + Ctrl also apperas to copy it to ~/Photos everytime The cursor always remains the half-square with the + icon in the middle while dropping. If I hold down ALT when I drop it, the cursor changes to a half-square with a ? icon in the middle of it and it will NOT copy it to ~/Photos, it leaves it where it is. From Konqueror: Dropping will NOT copy it to ~/Photos. The cursor is kind of a fist holding the thumbnail image as it drops it. Dropping + Ctrl will copy it to ~/Photos. The cursor is an arrow with a small box. Dropping + ALT will not copy it to ~/Photos. So it looks like it's a Konqueror issue. Anything else I can provide? Are there any plans to make it work the same in Konqueror?
David, there's nothing we can do here (IMHO) to solve this issue from f-spot... in this case, we're only _receiving_ drop events from Konqueror :( Can't you set the default drop behavior for K ? s
(In reply to comment #3) > there's nothing we can do here (IMHO) to solve this issue from f-spot... in > this case, we're only _receiving_ drop events from Konqueror :( should we close this?
I would second this, and ask for the above information to be raised against Konqueror...
This looks like a Konqueror bug, so I'm going to close it for now. Feel free to reopen it if it turns out to be an F-Spot issue.