You mustn't attempt to set the size in the resized() callback - that could obviously get into all kinds of recursive loops.
If it's the host that's resizing your component, then your plugin will just have to accept whatever it gets. If the resizing is being done by your own GUI (e.g. by a ResizableCornerComponent, etc) then you should apply your constraints to the size before setBounds gets called.
If it's the host that's resizing your component, then your plugin will just have to accept whatever it gets.
I wasn't aware of that. Host triggered size change was the main reason to put it into resize() - fully aware of the recursion taking place (multiple times).
Will move it to a derived class of ResizableCornerComponent as you have suggested.