You currently cannot delete a change detection if it is used by one more inter-comparisions. This is annoying if you use the batch change detection to generate lots of change detections and then produce an inter-comparison comparing them all. You might want to clean up the project and remove all but the most relevant change detections but this is not possible because of the aforemented linkage.
Inter-comparisons are "free-standing" and once they are generated do not link/reference/rely on the change detections that are used to generate them. Therefore it is not necessary to lock down the change detections in a project and prevent their deletion simply because they were once used in an inter-comparison. It should be possible to delete a change detection even while it is used in one or inter-comparisons within the project.
Feedback from @jb10016:
You currently cannot delete a change detection if it is used by one more inter-comparisions. This is annoying if you use the batch change detection to generate lots of change detections and then produce an inter-comparison comparing them all. You might want to clean up the project and remove all but the most relevant change detections but this is not possible because of the aforemented linkage.
Inter-comparisons are "free-standing" and once they are generated do not link/reference/rely on the change detections that are used to generate them. Therefore it is not necessary to lock down the change detections in a project and prevent their deletion simply because they were once used in an inter-comparison. It should be possible to delete a change detection even while it is used in one or inter-comparisons within the project.
FYI: This is a two second fix in GCD and simply requires the removal of one line of code!