[
https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi...
]
Michael Anstis commented on DROOLS-3406:
----------------------------------------
Great [~roger600] that helped a lot :-)
My next questions (sorry for doing on JIRA but our paths don't seem to be aligning at
the moment!), now I have a _custom_ shape for {{DecisionService}} using some code like the
following (it uses the base SVG shape from UX and adds a {{Line}} to it):
{code}
view = new SVGShapeViewImpl(name, primitiveShape, width, height, resizable);
final Line primitive = new com.ait.lienzo.client.core.shape.Line(0, height / 2, width,
height / 2)......
final SVGPrimitiveShape divider = SVGPrimitiveFactory.newSVGPrimitiveShape(primitive,
false, null);
view.addChild(divider);
{code}
I cannot use "scalable" as a {{Line}} has zero height (according to Lienzo) and
causes an "Infinity" error in some JSON internal to Lienzo and
{{WiresScalableContainer.scaleTo(..)}}. So I resize the width of the {{Line}} by adding a
{{view.addHandler(ViewEventType.RESIZE, new ResizeHandler()...)}} which works OK.. now.. I
want to (a) add a Control Point to the line to support moving it up and down (it'd be
nice to have a drag constraint too); when released I'd like a Command to execute, (b)
resizing the {{DecisionService}} from the Properties Panel does not lead to the {{Line}}
being resized (no surprise really, as it's not invoking the {{ResizeHandler}}.. any
ideas about this one? I see it also affects _core_ Stunner too (select a node so it's
Control Points/Toolbox are visible) and resize it using the Properties Panel. The
ControlPoints and Toolbox do not follow the resize from the Properties Panel.. anyway...
suggestions as always welcomed :-)
[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)