Community
Participate
Working Groups
When created a pin (input or output) can not be deleted directly (menu action to delete or hide is not available). Workaround : use the model explorer selection and commands.
This behaviour should has been desired at some point because the mechanism to prevent diagram deletion has been added to the normal behavior of those elements. I think it's has been implemented because pins are synchronised elements. So it appear normal that those element can not be deleted from the diagram. If specification has change we can remove this mechanism. Regards
OK, I should have been more precise. For OpaqueAction nodes, we should be able to delete or hide pins as there is no synchronization constraints. Concerning CallOperationAction and CallBehaviorAction nodes, yes it is a good idea that the end user can not delete pins as those pins must be kepts synchronized with invoked behavior. But it does not mean that "delete" and "hide" should be disabled. This is one solution that works but that does not help end user to understand. A better approach would be to give a message to tell that deletion is not permitted because of this synchronization. End user would learn and understand this synchronization rule through usage. Currently he/she thinks that this is a bug as there is no explanation. Concerning "hide", it should remain available. As an end user I might be interested in hiding a pin that is not yet connected. Remember that diagrams are only a partial view of the model. As some classes or blocks do not show all attributes or all ports, one can imagine that an action does not display all parameters. The synchronization rule must ensure that model is consistent with as many parameters in invoked behavior as pins in action element, but perhaps not all visible in the action node representation on the current diagram... As a conclusion, I suggest putting "hide" and "delete" always available but with restriction on "delete" for callAction nodes (CallBehavior and CallOperation) to display a "popup" warning message explaining that modifications should occur at invoked behavior directly (with eventually a link to this invoked behavior in model explorer)
Verified OK Closed
