Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Emptying trash deletes too many files.

Kommentare

6 Kommentare

  • SFA

    Each image will have multiple associated files (in operating system file handling terms) if you are deleting the source file.

    Preview, thumbnail, edit instructions, focus mask, for example. Add the Source file and that give you 5x the source image count.

    There may be others if you have used Layers or LCC features, etc.

     

    0
  • David Willis

    Ah, I see. That is needlessly confusing and poor UX design. I'm glad to understand what's going on though. Thank you!

    0
  • gb

    Maybe it's a subtle way of C1 telling us why the deletion process takes so long. LOL.

    0
  • SFA

    David,

    Maybe you are right but I guess that it's a question of reporting according to User expectations about numbers within the Application and then relying on what the Operating System reports (no point in trying to duplicate and monitor the OS status information) during final delete activity.

    I don't really give it any thought since I worked out what is going on.

    If C1 reports something like "Images" deleted but the OS reports "files" being the number of files being zapped from the Trash Bin that would seem to me to be a reasonable way of reporting of both aspects - once one is satisfied that what is being reported is what one is expecting.

    0
  • gb


    Maybe they could change the progress wording to "Deleting image and ancillary files......"
    to avoid stressing out first time users.

     

    1
  • David Willis

    "I don't really give it any thought since I worked out what is going on."

    Yeah, now that I understand I won't either. Thanks for letting me know!

    0

Post ist für Kommentare geschlossen.