I'm not really happy with my proposed solution for issue http://argouml.tigris.org/issues/show_bug.cgi?id=5853
Essentially the problem seems to be that MDR provides us with both a remove event (when a model element is removed from some container) and also a delete event when a model element is actually deleted from the repository. The MDR model event pump converts the remove event and delete event to our own property event wrappers (with our DeleteInstanceEvent wrapping the MDR delete event). We are looking for DleteInstanceEvent to delete Figs, tree items and items in the target manager. Eclipse only seems to give a remove event as far as I can see. If an element is removed from its container then it is also considered out of the repository. The euml model event pump converts an eclipse remove event to both our own style remove events but also our own delete event (DeleteInstanceEvent). The result being that if a model element is removed to be added to some other part of the model then we have actually received a delete event and end up deleting relevant Figs, tree items. The item also gets deleted from the TargetManager and so the property panel showing the element also disappears. A side effect of changing navigability in eclipse uml is that this remove and add takes place. Hence changing navigability makes the property panel for the association end disappear. So, am I missing something. Is there a way I can determine a delete event from eclipse UML as opposed to remove? Bob ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2397565 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
