Community
Participate
Working Groups
The current drag and drop strategy mechanism is not used currently to implement this specific behavior. This specific drop should be handled relying on the dnd strategy.
The specific drop is the drop of a classifier to create a property part on the composite structure
New Gerrit change created: https://git.eclipse.org/r/55849
Gerrit change https://git.eclipse.org/r/55849 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=1028fbb9f2b46f054b4d8e8a66291abc310e4fbf
Hi, it is impossible to drop a class in to compartment of a composite. It does not create a propertye typed by the dropped class. It has be bone on Neon
New Gerrit change created: https://git.eclipse.org/r/58519
New Gerrit change created: https://git.eclipse.org/r/58518
New Gerrit change created: https://git.eclipse.org/r/58520
Gerrit change https://git.eclipse.org/r/58518 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=f17c27f6b74a8aa6987f236b645f21fec7227ac0
This contribution breaks the tests for SysML 1.1, as this drop strategy is enabled e.g. in SysML Internal Block Diagram. However, this strategy won't work in this diagram: !ENTRY org.eclipse.papyrus.infra.gmfdiag.dnd 4 0 2016-01-07 13:29:31.943 !MESSAGE Unexpected Error !STACK 0 org.eclipse.core.runtime.AssertionFailedException: null argument:failed to create a view at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.gmf.runtime.diagram.ui.commands.CreateCommand.doExecuteWithResult(CreateCommand.java:96) at org.eclipse.gmf.runtime.emf.commands.core.command.AbstractTransactionalCommand.doExecute(AbstractTransactionalCommand.java:247) at org.eclipse.emf.workspace.AbstractEMFOperation.execute(AbstractEMFOperation.java:150) at org.eclipse.gmf.runtime.diagram.ui.commands.ICommandProxy.execute(ICommandProxy.java:68) at org.eclipse.gef.commands.CompoundCommand.execute(CompoundCommand.java:129) at org.eclipse.gef.commands.CompoundCommand.execute(CompoundCommand.java:129) at org.eclipse.papyrus.infra.gmfdiag.dnd.strategy.TransactionalDropStrategy$1.doExecuteWithResult(TransactionalDropStrategy.java:54) [...] SysML already provides a drop strategy for this case that works in IBD, but it is now conflicting with this new strategy. This causes at least the following test failures: org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropDataTypeOnBlockCpt org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropBlockOnBlock org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropDataTypeOnBlock org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropFlowSpecOnBlock org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropActorOnBlockCpt org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropActorOnBlock org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropFlowSpecOnBlockCpt org.eclipse.papyrus.sysml.diagram.internalblock.tests.dnd.altdrop.TestTypeDropOnBlock.testDropBlockOnBlockCpt
New Gerrit change created: https://git.eclipse.org/r/66486
I'll fix Comment 9
https://git.eclipse.org/r/67049
Tests fixed by Camille contribution