[
https://issues.jboss.org/browse/DROOLS-3894?page=com.atlassian.jira.plugi...
]
Roger Martinez commented on DROOLS-3894:
----------------------------------------
Yep [~McCloud] [~manstis], good catch, this is a shared feature between both editors, so
for sure this bug also applies for BPMN.
So agree, the thing is that if behaves different when using mouse rather than keyboard, it
also generates some confusion. In general, in Stunner, a shape can only be on top of
another if it's a child (or boundary) node. This is how it behaves by using mouse
events, but not when using the keyboard.
Due to the above reason I consider this as a bug, and IMO the solution IMO relies on just
defining the "limits" where a shape, using the keyboard, can be moved to/from.
This way using the keyboard the user will be not able to change parent/childs, but will be
allowed to move the shape inside the actual parent's bounds. Otherwise providing
visual feedback for containment/docking operations can be a bit hard.
Decision Nodes not correctly anchored in Decision Service when using
keyboard arrows to move nodes
--------------------------------------------------------------------------------------------------
Key: DROOLS-3894
URL:
https://issues.jboss.org/browse/DROOLS-3894
Project: Drools
Issue Type: Bug
Components: DMN Editor, Stunner
Affects Versions: 7.18.0.Final, 7.20.0.Final
Environment: RHPAM 7.3.0.GA
Reporter: Duncan Doyle
Assignee: Michael Anstis
Priority: Major
Labels: drools-tools, stunner
If you use a Decision Service, and put Decision Nodes in the service box, the anchoring
of the nodes in that service is messed up when you start moving around the nodes using the
arrow keys on your keyboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)