Hi Doru, Indeed, TRMultiCompositeShape>>announcer should not be called. In your case, a multiCompositeShape was added in the Canvas, which should not happen. I fixed this, there was a bug when pushing back shapes. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Nov 1, 2014, at 7:03 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: Hi, I think we have a problem with announcer from TRMultiCompositeShape. It is implemented as if it should not be called, but TRCanvas>>shapeWithAction: eventClass forPositionInPixels: position calls it. So, we have a problem. I observed the problem when creating edges with RTMondrianViewBuilder. For example: view := RTMondrianViewBuilder new. view shape label text: #asString. view nodes: (1 to: 100). view shape orthoHorizontalLine color: Color veryLightGray. view edgesFrom: [:x | x // 10]. view horizontalTreeLayout layered. view And then click on an edge. Doru -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev