Why a Continuity Photo Can Display Without Being Cleaned Up with Its Record
A continuity photo showing in the interface does not mean the app’s copy of the file is in a position to be cleaned up. Deletion must also distinguish a photo that belongs exclusively to one item from one still linked to another record.
Seeing the photo is one thing; cleaning up the corresponding file with the record is another.
Display and cleanup are different operations
Cards, detail views, references, and the comparison screen all display photos, but deletion needs to know where the file to be handled is. The visible image or its label alone is not proof that the corresponding file was located or removed.
Some photos (for example certain quick-create linked covers and nearby-received photos) may have display content without a reliable local file trail. What can be confirmed is that both cases can exist; it is not evidence that a particular number of files will remain after a deletion, which needs a check of the actual files.
Deleting a take also removes continuity assets beneath it
The take-list deletion confirmation expressly states that continuity assets under the deleted take are removed with it and that the operation cannot be undone. Deleting the record is therefore not merely a way to hide it from a list.
The deletion confirmations across episode, scene, shot, take, and project levels also warn that the operation cannot be undone. Review the level and its associated records before deleting, rather than assuming a recovery entry will appear afterward. What Sign-Out, Account Deletion, and Project Deletion Actually Remove addresses a separate part of the deletion story.
A continuity-library deletion distinguishes exclusive photos from shared ones
The continuity-library confirmation separates photos belonging exclusively to the item from photos still attached to other takes. The former are included when that library item is deleted; the latter are left with their other take links. Two screens showing the same picture do not, by themselves, establish that this deletion will remove every displayed instance or file.
Deletion can involve both record links and local files, but a record no longer appearing is not proof that its file is gone from this computer. Inspect the actual links before drawing conclusions about which photos are exclusive.
Previously exported handoffs and external originals are separate
Deleting an in-app record does not rewrite handoff files that were already written or sent. Nor should deletion of an in-app copy be confused with deletion of a photo or video original in a device photo library, a camera card, or an external media archive.
Uninstalling the app or erasing the device can remove data the app itself stores. That does not prove that images can be recovered after reinstallation or on another device. Cross-device recovery is a separate question not verified here.
FAQ
Why can a picture still display without a usable deletion path?
Display and file cleanup are not the same thing; being able to display does not mean the information needed for cleanup is complete.
Does deleting a take affect the continuity assets under it?
Yes. The take-deletion confirmation states that the continuity assets under the record are removed and the operation cannot be undone.
Does deleting a continuity-library item remove every copy of the image?
Do not assume so. The confirmation distinguishes exclusive photos from those still linked to other takes.
Do previously exported handoffs change after an in-app deletion?
No. An already written handoff is not rewritten by that deletion; the current state of local files needs a separate check.
Axiom One LLC — SlateX