Rómeó Nagy

Hi! Unfortunately I found **a new major problem in this particular bug** which is not anymore just an UX problem. Stick to the example gif what I reported. When user...

The auto placement stuff works if the task has no out sequence flow. In that case it cannot be a problem because it will be sure that only one out...

Multiple outcoming sequence flows can be at start gateways. Multiple incoming sequence flows can be at end gateways.

Or do not take it intolerant its just an option but please consider also to drop this kind of auto placement stuff and revert back to that method where user...

> dragging out = full control where to put it (old behavior) > clicking = placing automatically at an appropriate place I did not know about it. Thanks for pointing...

It is still a problem that the automatic placement render the task on the sequence flow (like it was merged) and hard to see what is happening.

Sorry, in the mean time I found the problem that this plugin is not converge to 0 time (absolute) but converge to new Date() (relative) time. So to restart the...

Hi! I upgraded to 0.3.0 version, but unfortunately it is still not tracing camunda:decisionRef changes nor input/output parameters.

Thank you nikku! Now it trace camunda:decisionRef change indeed. I Used as following: ``` var BpmnModdle = require('bpmn-moddle'), BpmnCamundaModdleDescriptor = require('camunda-bpmn-moddle/resources/camunda'); new BpmnModdle({ camunda: BpmnCamundaModdleDescriptor }).fromXML(xml, function(err, definitions) { ......

Ok, when I call `Differ.diff(adefs, bdefs)` on the two parsed BPMNs it returns and indicate the input/output parameter "_changed", but I see no old-new values descriptor in the "attrs" property.