I expect that CX will continue to behave as if the page still exists in the
comic; i.e., the row will remain in the database, viewing that comic's
details will show a missing page for the one that was deleted, and the
number of pages reported for the comic will be unchanged.
We have some code in place for rescanning the library to update comics
that've been changed like that, but there's nothing exposing that in the
user interface yet. I've plans to expose that in a more comprehensive admin
interface.
On Thu, Jan 9, 2020 at 8:07 PM Guy Incognito <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
CX is allowing me to do a number of things that weren’t possible when
using CR – in this case, identifying duplicate images that can be removed
from comic archives.
Using command line 7zip, it’s very easy to delete a specific file from
within an archive once you know the file name. In most instances, the
deleted image would be the last page of the cbz...but in some, it will be
the first – which would be the image identified as page 0 in the CX PAGES
table.
Do you have any thoughts as to how CX react to this happening?
