[Moose-dev] Re: Roassal TRCompositeShape regression

Hi I'd like to break into your discussion, so we won't talk about the same in two threads. Composite shapes should, to outer world, act line normal shapes, which could be moved, resized, used callbacks on and they should act like we expect usual shapes to. Thing is it is not quite clear what is this "expected" behavior and in my opinion it depends on actual usage of composite shapes, especially with resizing and callbacks. One might want to resize only one border-like shape and keep rest as it is, or to resize all subshapes to new size, or resize all proportionally, like increase width by 50 %. The same is there for callbacks, when we might want to have callback for every change of extent of any inner shape, or we might want to have callback only when one of them changes extent, or only when whole shape changes extent (because when we change extent of shape in the center of larger one, it does not change extent of whole shape). I thought about using replacable blocks for composite shapes actions like adding callbacks, resizing or moving composite shape, reaction to moving or resizing sub-shapes etc. Jan abergel wrote -- View this message in context: http://forum.world.st/Roassal-TRCompositeShape-regression-tp4816726p4818430… Sent from the Moose mailing list archive at Nabble.com.