Closed GoogleCodeExporter closed 9 years ago
What is the best solution? Cancel the movement, if it is done via docker and an
attachment on that position is not allowed?
Original comment by NicoPete...@gmail.com
on 21 Apr 2008 at 3:38
Original comment by W.Tsches...@gmail.com
on 22 Apr 2008 at 11:49
Gero, Willi and I discussed to introduce a new attachment-relation between
nodes and
to not use the docker-magnet-principle for this, anymore. User tests have shown
that
the two different ways for moving a bpmn intermediate event is not intuitive.
Furthermore, priority is set to high.
Original comment by NicoPete...@gmail.com
on 22 Apr 2008 at 1:38
we decided to use the following concept:
if an intermediate event is positioned over a subprocess's edge while dragging,
the
subprocess's edge is highlighted and if the mouse button is released, it will be
attached. but if the intermediate event is completely dragged into the
subprocess and
the mouse button is released, it will be added as a child of the subprocess.
Original comment by NicoPete...@gmail.com
on 22 Apr 2008 at 2:10
Must be solved as soon as possible.
Original comment by NicoPete...@gmail.com
on 22 Apr 2008 at 2:32
Fixed this issue. Now if u drag a node with at least one docker, the plugin
DragDropReszise is checking if this node can be attached to the underlying node
as
well. The Config Parameter ORYX.CONFIG.BORDER_OFFSET give the value for area
where is
checked for attachment.
Revision 219
Original comment by W.Tsches...@gmail.com
on 29 Apr 2008 at 3:41
Original comment by NicoPete...@gmail.com
on 5 May 2008 at 11:16
Original issue reported on code.google.com by
pkersti...@gmx.de
on 29 Nov 2007 at 4:01