[Moose-dev] Re: Issue 842 in moose-technology: ROTranslatingShape mouse hotspot mis-alignment

Updates: Labels: Component-Roassal Comment #12 on issue 842 by alexandr...(a)gmail.com: ROTranslatingShape mouse hotspot mis-alignment http://code.google.com/p/moose-technology/issues/detail?id=842 I agree with what you said. The state is the following: more I work on the translation shape, slower roassal become to be (e.g., each elementAt: and contains: need to go through the shape chain in case there is a ROTranslationShape somewhere) and more complex it become. Now, I am wondering whether subclassing ROElement will not be an easier way to solve your problem. Maybe something like ROCompositeElement. Does this make sense?