We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Hello,
Durning development we have accured couple of issues that we want to disscuss with you.
To make it easier we have prepared sample project, all you need is to unzip folder and open index file. At bottom there is listed problems with example of diagram useage in our project.
List:
Problem 1: How to initialize the position of the diagram to start from the top, without unnecessary offset. What is the proper algorithm for setting the diagram position?
Problem 2: Drag and drop TextAnnotation into Lane1. Move element to some other position. Notice that element size growing 20px on every move.
Problem 3: Drag and drop TextAnnotation into Lane1. Clear text and click to focus on other element. Then try to change text in droped TextAnnotation and look at console error.
Problem 4: Drag and drop TextAnnotation into Lane1. Why TextAnnotation is not resizable like other shapes ?
Problem 5: Drag and drop some BPMN shape into Lane 1 or Lane 2 .
The collectionChange event arguments do not have parentId information in the element property (args.element.parentId).
We expect information in the arguments about which Lane is the parent of the element being laid.
We checked that nodes collection (diagram.getObject('swimlane').shape.lanes[0].children) doesn't contains added shape on event collectionChanged and drop event as well.
Problem 6: Drag and drop two BPMN shapes into Lane 1 or Lane 2.
A: Correct scenario: Select first dropped shape (click on it to select/focus) and try to move to some other position. Event positionChange reaised correct
B: Uncorrect scenario: Try to move second shape without first clicking (do not select/focus). Bug: Event positionChange NOT raised
Problem 7: Drag and drop two BPMN shapes into Lane 1 or Lane 2 and try to use new connector to connect shapes.
The connectionChange event is raised to many times on move. Should be only on drop/leave connector.
There is no completed/unequivocal state, meaning connection done.
|
Query |
Response |
|
Problem 1: How to initialize the position of the diagram to start from the top, without unnecessary offset. What is the proper algorithm for setting the diagram position? |
Could you please confirm us whether you need to render diagram without setting width and height property or diagram node without setting offset(offsetX and offsetY)?. Please share us more details such as explain your requirement in detail with screenshot or video. |
|
Problem 2: Drag and drop TextAnnotation into Lane1. Move element to some other position. Notice that element size growing 20px on every move.
Problem 3: Drag and drop TextAnnotation into Lane1. Clear text and click to focus on other element. Then try to change text in droped TextAnnotation and look at console error.
Problem 4: Drag and drop TextAnnotation into Lane1. Why TextAnnotation is not resizable like other shapes ?
Problem 5: Drag and drop some BPMN shape into Lane 1 or Lane 2 .
The collectionChange event arguments do not have parentId information in the element property (args.element.parentId).
We expect information in the arguments about which Lane is the parent of the element being laid.
We checked that nodes collection (diagram.getObject('swimlane').shape.lanes[0].children) doesn't contains added shape on event collectionChanged and drop event as well.
Problem 6: Drag and drop two BPMN shapes into Lane 1 or Lane 2.
A: Correct scenario: Select first dropped shape (click on it to select/focus) and try to move to some other position. Event positionChange reaised correct
B: Uncorrect scenario: Try to move second shape without first clicking (do not select/focus). Bug: Event positionChange NOT raised
Problem 7: Drag and drop two BPMN shapes into Lane 1 or Lane 2 and try to use new connector to connect shapes.
The connectionChange event is raised to many times on move. Should be only on drop/leave connector.
There is no completed/unequivocal state, meaning connection done.
|
We are able to replicate an issues at our end. We will validate your issues and provide you an more details soon. |
Hi,
We prepared new example to explain Problem 1 from previous post.
Problem 1: How to initialize the position of the diagram
to start from the top, without unnecessary offset. What is the proper algorithm
for setting the diagram position? In top left corner, not center inside
container(explained with pictures in example).
|
Query |
Response | |
|
We prepared new example to explain Problem 1 from previous post.
Problem 1: How to initialize the position of the diagram to start from the top, without unnecessary offset. What is the proper algorithm for setting the diagram position? In top left corner, not center inside container(explained with pictures in example).
|
In order to put the swimlane at the top left corner, we need to set swimlane offsetX and offsetY to the half of their width and height. Please refer to an code example and sample below.
Code example:
Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/Problem1modified-508571016
| |
|
Problem 2: Drag and drop TextAnnotation into Lane1. Move element to some other position. Notice that element size growing 20px on every move.
Problem 3: Drag and drop TextAnnotation into Lane1. Clear text and click to focus on other element. Then try to change text in droped TextAnnotation and look at console error.
Problem 4: Drag and drop TextAnnotation into Lane1. Why TextAnnotation is not resizable like other shapes ?
Problem 5: Drag and drop some BPMN shape into Lane 1 or Lane 2 .
The collectionChange event arguments do not have parentId information in the element property (args.element.parentId).
We expect information in the arguments about which Lane is the parent of the element being laid.
We checked that nodes collection (diagram.getObject('swimlane').shape.lanes[0].children) doesn't contains added shape on event collectionChanged and drop event as well.
Problem 6: Drag and drop two BPMN shapes into Lane 1 or Lane 2.
A: Correct scenario: Select first dropped shape (click on it to select/focus) and try to move to some other position. Event positionChange reaised correct
B: Uncorrect scenario: Try to move second shape without first clicking (do not select/focus). Bug: Event positionChange NOT raised
Problem 7: Drag and drop two BPMN shapes into Lane 1 or Lane 2 and try to use new connector to connect shapes.
The connectionChange event is raised to many times on move. Should be only on drop/leave connector.
There is no completed/unequivocal state, meaning connection done.
|
We have logged a defect report for all the reported issues. The fix for these issues will be available on 11th November, 2019.
You can track the status of the issues from the below feedback link.
|
|
Query |
Response |
|
Problem 2: Drag and drop TextAnnotation into Lane1. Move element to some other position. Notice that element size growing 20px on every move.
Problem 3: Drag and drop TextAnnotation into Lane1. Clear text and click to focus on other element. Then try to change text in droped TextAnnotation and look at console error.
Problem 5: Drag and drop some BPMN shape into Lane 1 or Lane 2 .
The collectionChange event arguments do not have parentId information in the element property (args.element.parentId).
We expect information in the arguments about which Lane is the parent of the element being laid.
We checked that nodes collection (diagram.getObject('swimlane').shape.lanes[0].children) doesn't contains added shape on event collectionChanged and drop event as well.
Problem 6: Drag and drop two BPMN shapes into Lane 1 or Lane 2.
A: Correct scenario: Select first dropped shape (click on it to select/focus) and try to move to some other position. Event positionChange reaised correct
B: Uncorrect scenario: Try to move second shape without first clicking (do not select/focus). Bug: Event positionChange NOT raised
|
We are glad to announce that our patch release (v17.3.30) is rolled out successfully and In that release, we have added the fix for reported issue.
Please upgrade to the latest version packages to resolve this issue.
|
|
Problem 4: Drag and drop TextAnnotation into Lane1. Why TextAnnotation is not resizable like other shapes ? |
We don’t have option to resize an TextAnnotation. We have logged “Resize support for text Annotation node” as a feature. You can track the status of the feature from the below link.
|
|
Problem 7: Drag and drop two BPMN shapes into Lane 1 or Lane 2 and try to use new connector to connect shapes.
The connectionChange event is raised to many times on move. Should be only on drop/leave connector.
There is no completed/unequivocal state, meaning connection done.
|
The connectionChange event raises continuously when we move the mouse on the node to establish a connection. We don’t have completed state for this event. It is a default behavior of our diagram control. |
