Bug 1196403 - first and last waypoints of sequence flow DI needs update if inside a lane
Summary: first and last waypoints of sequence flow DI needs update if inside a lane
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER4
: 6.2.0
Assignee: Tihomir Surdilovic
QA Contact: Kirill Gaevskii
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-25 22:05 UTC by Tihomir Surdilovic
Modified: 2020-03-27 19:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:08:34 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
DI points position in Business Process Source after fix (1.18 MB, application/octet-stream)
2015-10-26 12:54 UTC, Kirill Gaevskii 		no flags Details
View All

Description Tihomir Surdilovic 2015-02-25 22:05:27 UTC 
di waypoints of sequence flows (first and last) if they lie within a lane
Comment 2 Kris Verlaenen 2015-02-26 02:38:48 UTC 

*** This bug has been marked as a duplicate of bug 1196267 ***
Comment 3 Tihomir Surdilovic 2015-02-26 04:27:23 UTC 
this bug is specific to lanes where the  bug 1196267 for subprocesses. there is a small difference in the fix and i would like to ask if we could keep them separate

for this one fix is in
6.2.x https://github.com/droolsjbpm/jbpm-designer/commit/aaef4aca1698dd3b7ba5f5e89f25e7c0e565bba5


master https://github.com/droolsjbpm/jbpm-designer/commit/b90c080e5ae506c76f803858b3561c380c436064
Comment 6 Kris Verlaenen 2015-10-01 21:31:34 UTC 
I believe this was fixed in master months ago (the only issue was the cherry-pick to 6.2.x)
Comment 7 Kirill Gaevskii 2015-10-26 12:53:35 UTC 
The first and last Waypoint in the BPMNEdge DI element for the Sequence Flow have sum of coordinates relative to the top-left corner and the swimlane, instead of being absolute (diagram-relative) coordinates. (See attachment)

P.S. I guess commit is hard readable and it can cause some inaccuracies like this one. So maybe it is not so bad to make some refactoring of it.
Comment 8 Kirill Gaevskii 2015-10-26 12:54:21 UTC 
Created attachment 1086513 [details]
DI points position in Business Process Source after fix
Note You need to log in before you can comment on or make changes to this bug.