[
https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi...
]
Michael Anstis commented on DROOLS-3406:
----------------------------------------
All going good [~roger600]; but I have a question.
Do I have to _map_ Lienzo/Wires events (in response to drag/move/resize etc) in
{{WiresShapeViewExt.addHandler(..)}} to Stunner {{ViewHandler}}?
I have some new Lienzo/Wires events being raised for moving the "splitter" that
I _can_ handle in my new {{AbstractCanvasHandlerRegistrationControl}} implementation (to
get access to a {{CommandManager}} etc) however looking at existing code it looks like I
should have {{WiresShapeViewExt.addHandler(..)}} handle the Lienzo/Wires event and
re-raise as a Stunner {{ViewHandler}} event... problem is that moving the
"splitter" cannot re-use one of the existing {{ViewEventType}} and adding a new
type seems more effort than it's worth (since it's an {{enum}}).
[DMN Designer] Decision Service splitter should be movable
----------------------------------------------------------
Key: DROOLS-3406
URL:
https://issues.jboss.org/browse/DROOLS-3406
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.15.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
Priority: Major
Labels: drools-tools
The _splitter_ within a Decision Service is static.
It needs to be movable (vertically) maintaining it's alignment with the Decision
Service bounds. At this point we need to either decide to add _result_ decision(s) and
_encapsulated_ decisions to the Decision Service by Command (depending on where the node
is dropped) or update the Marshaller to determine the type of decision based on its
vertical positioning and location of the _splitter_.
h2. Acceptance test
Decision state is updated according to _splitter_ movement. Example if area of result
decision expanded so some decision belongs there now, this decision should have state
_rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)