Delete newly created folder if import is cancelled

  • 1
  • Idea
  • Updated 2 years ago
When I import photo's into a new LR folder, create the folder and then decide to cancel the import after all, LR will not show the newly created folder in its own folder structure, but the folder is stil there on OSX level.

LR will, for some reason, not delete the folder, thus introducing an inconsistency between the folder mapping and the real folder structure. This is a (very!) undesirable  situation.

Please change LR in such a way, that it will maintain consistency between the folder structure and content within itself and the OSX world. 

Earlier I posted this as problem, but it was recommended I re-post this as an idea. Actually I still think this is a problem / oversight in the design.
Photo of Hans Douma

Hans Douma

  • 73 Posts
  • 4 Reply Likes
  • disappointed

Posted 2 years ago

  • 1
Photo of Tom Mickow

Tom Mickow

  • 326 Posts
  • 112 Reply Likes
No offense Hans, but I disagree.  I think your process is introducing a problem that isn't necessarily Lightroom's fault or responsibility to clean up after.

If you create the folder in the Lr import panel, there's nothing that prevents you from switching to another app and placing some files in that folder, moving it, deleting it, etc.  It would be dangerous for Lr to assume it should be deleted if you cancel the Import.

Let's extend the scenario to other apps, like Microsoft Word.  When I'm saving a document in Word, I can create new folders from the save dialog box, but then cancel or save the document elsewhere.  Word doesn't clean up after me and delete the folder I just created.  I have to go take care of that myself as a separate process.

With regards to consistency between Lr's Folder panel and the real folder structure, that's never existed.  Lr's Folder panel only shows folders where you've told it images you want it to manage are located.
Photo of Hans Douma

Hans Douma

  • 73 Posts
  • 4 Reply Likes
Tom, I can see your point. Still in my view an app like LR does not compare to Word it that sense. I do not create a photo in LR as I create a document in Word. I just want to load photo's to a certain location and if that location does not yet exist, it must be created. That is something done from within LR. I do not go out of LR to OSX deliberately to do that. Currently it is LR itself that is directing me to OSX level. It could (and should) create a folder itself via an API or so, as it does when I tell it to put the photos into a subfolder. (In that situation it is not necessary for me to create that sub folder). In my view it is a LR responsibility to create a folder and load the photos into that folder and if I abandon that process, it should clean up, just as CMD-Z would do. Of course canceling an import to an existing folder should not delete that folder. So it is a combination: create folder>load photos into folder. If cancelled reverse that process. If  importing to an existing folder and cancel, leave the folder alone and just delete any photos just imported during this session. In short: clean up after canceling. 
Photo of Tom Mickow

Tom Mickow

  • 326 Posts
  • 112 Reply Likes
Yep, I can see your point too...I just don't happen to agree for the reasons stated earlier.  :)

I'd be much happier if our friends at Adobe concentrated on improving Lr's speed & stability rather than fixing bits like this that can easily be worked around.

Btw, have you ever created the folder first in the Folders panel and then imported directly into it by right-clicking on it and choosing "Import to this Folder..."?  That process change might help lessen the confusion.  Even if you decided not to import, the folder would show up in Lr's Folder panel until you removed it.
Photo of Butch_M

Butch_M

  • 292 Posts
  • 112 Reply Likes
I agree, theoretically, it makes sense that Lr could do this housecleaning ... however, in practice ... Lr is simply utilizing direct access to the OS file system to create, organize and even delete files/folders.

Since your images are not actually imported into the Lr application ... they are 'referenced' as to their location on your system by the Lr library, which is why Lr doesn't clean up after such commands.

We've had enough issues with Adobe products arbitrarily deleting files as a result of other issue lately ... I don't think we need more.
Photo of Hans Douma

Hans Douma

  • 73 Posts
  • 4 Reply Likes
Sure, obviously I am talking about a properly functioning program. Anyway, folder management clearly is a weak spot in LR, either intentionally or unintentionally. Coming from Aperture it is just something to remember......
Photo of Butch_M

Butch_M

  • 292 Posts
  • 112 Reply Likes
You are making unfair comparisons ... as someone who uses both apps ... and would have much preferred to lean strongly to only using Aperture until Apple dropped support for it ... you have to remember that Lightroom has never stored files within the catalog file itself like Aperture was capable of.  I think if you look, folders created in Aperture for referenced images, behave the same as Lightroom. It's not a matter of weakness on Lightroom's part. It's just different. Not everything that Aperture does/did is best practice either ... if you learned one before the other.