Currently, changes to a Part Catalog are not passed to the Aggregation class by the aggregation components. The issue is how to handle changes, as if a Catalog has been emptied already and changes are made to the input Catalog, this would refill the whole catalog, hence adding again also the parts that were already placed.
One option would be to keep track of the input catalog in a separate variable, compare the new input one with the stored version, and update only the ones that changes with the difference between the stored one and the input one.
Currently, changes to a Part Catalog are not passed to the Aggregation class by the aggregation components. The issue is how to handle changes, as if a Catalog has been emptied already and changes are made to the input Catalog, this would refill the whole catalog, hence adding again also the parts that were already placed. One option would be to keep track of the input catalog in a separate variable, compare the new input one with the stored version, and update only the ones that changes with the difference between the stored one and the input one.