https://bugs.kde.org/show_bug.cgi?id=371990
--- Comment #22 from Ralf Habacker <ralf.habac...@freenet.de> --- (In reply to clushkou from comment #20) > I tried to fulfill your request in comment #17, but do not understand how to > achieve this. If I simply move the calls to ComponentWidget, I get a crash > on undo because restoring of child element does not work. > In addition, if the code needs to be added to ComponentWidget, the same > adaption is needed in all widgets that allow child Pins / Ports. I see. For the record: umbrello uses saveToXMI and loadFromXMI() to handle xmi file save/load, object (de)serialisation on copy/paste between same and other umbrello instances and undo framework so it would be nice to hold related stuff together and to implement stuff in the same way if possible to reduce req What I did: I created a component widget with ports and saved it into a xmi file. Inspecting this file shows that the component widget and the pin widgets does not have any direct association. The association is performed by the related UML:Component which has UML:Port as child. The in-memory representation changes this behavior by adding a direct association former with m_pow and now this QGraphicsItem child api. -- You are receiving this mail because: You are watching all bug changes.
