Moving events using the docker about oryx-editor

[GoogleCodeExporter]

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 [email protected] on 21 Apr 2008 at 3:38

[GoogleCodeExporter]

Original comment by [email protected] on 22 Apr 2008 at 11:49

[GoogleCodeExporter]

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 [email protected] on 22 Apr 2008 at 1:38

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

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 [email protected] on 22 Apr 2008 at 2:10

[GoogleCodeExporter]

Must be solved as soon as possible.

Original comment by [email protected] on 22 Apr 2008 at 2:32

• Added labels: Priority-Critical, Schedule-ShortTerm
• Removed labels: Priority-High

[GoogleCodeExporter]

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 [email protected] on 29 Apr 2008 at 3:41

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by [email protected] on 5 May 2008 at 11:16

• Changed state: Verified