Community
Participate
Working Groups
We need to support drag-and-drop of protocol where the drop target is a capsule part (or actually the contour/border of a capsule part). This should then create an external behavior port of the capsule used to type that capsule part. This is also related to the new child menu which allows you to right click on a capsule part in the model explorer, and then create a port. The same shall of course be possible to achieve using drag-and-drop. Currently in the latest Papyrus-RT build, only a stop-sign is shown when hovering and selecting a capsule part as a drop target. So to summerize: 1) DnD a Protocol on a CapsulePart border creates a RT Port on the related Capsule 2) From the Model Explorer, a child menu on a CapsulePart should allow the creation of an RTPort on the related Caspule
(In reply to Celine Janssens from comment #0) > 2) From the Model Explorer, a child menu on a CapsulePart should allow the > creation of an RTPort on the related Caspule Just to be clear: This case with using the UMLRealTime new child menu already works, i.e. you can already now right click on a capsule part in the model explorer and select UMLRealTime > Port and you get an external behavior port crated on the capsule typed by the capsule part (and the port gets automatically displayed on the capsule part, although it is still a bit too big, see Bug 476882 Comment 5).
A drop strategy for Protocols on CapsulePart should then be allowed to create a port. It should be an External Behavior Port. to complete content of this bug: once system protocols will be clearly identified, it should not be possible to drop a system protocol on the border of a capsule part to create a port ? To reformulate, are the system protocols only dedicated to SAP or they can be used for external behavior ports?
(In reply to Remi Schnekenburger from comment #2) > to complete content of this bug: once system protocols will be clearly > identified, it should not be possible to drop a system protocol on the > border of a capsule part to create a port ? To reformulate, are the system > protocols only dedicated to SAP or they can be used for external behavior > ports? System protocols are only used for SAP is user models. So it does not make sense to drag-and-drop a system protocol onto the border of capsule part, only to drag-and-drop a system protocol to the inside of the capsule itself, i.e. to create an SAP.
This one is in state ASSIGNED, but to whom is it assigned?
When important aspect to consider here, is the placement of the ports. Since we already have the functionality of placing the ports on the capsule part relative to the position of the port on the capsule, see Bug 482599, we have the need for the opposite here. Whenever you drop the protocol on the border of the capsule part to create a port on the corresponding capsule, the position of the port on the capsule should be relative to the position of where the port is placed on the capsule part. The same is of course applicable for the case of using the port creation tool from the palette according to Bug 492368.
I assume that this one can be put into resolved fixed (and possibly also verified fixed), since the work with Bug 492368 also fixed the drag-and-drop case (including the port creation tool case). I suggest that we put this one into resolved/verified fixed (I do not have the access right to do so).
(In reply to Peter Cigehn from comment #6) > I assume that this one can be put into resolved fixed (and possibly also > verified fixed), since the work with Bug 492368 also fixed the drag-and-drop > case (including the port creation tool case). I suggest that we put this one > into resolved/verified fixed (I do not have the access right to do so). Céline, do you agree? Sorry, I hadn't realized that my work overlapped with this bugzilla.
Yes I agree ! :)
Verified as part of Bug 492368 Comment 13.
Closing as already verified fixed.
