Jules, it seems to me that ResizableEdgeComponent should have a setBoundsConstrainer() method.  At the very least, since there's no way to 'unset' a constrainer that was defined in the constructor, one is reliant on destructor ordering to ensure that the resizer gets deleted before the constrainer.


Being able to call myResizableEdgeComponent->setBoundsConstrainer(nullptr); in the owner class destructor seems like good practice to me, and being able to switch out a constrainer model on the fly could also have merit.