Community
Participate
Working Groups
If a connection starting at one anchor and ending in the same is re-connected to another anchor it might be reverted.
Created attachment 213866 [details] fix for this bug I've found the bug in Graphiti 0.8.0 but the buggy code is the same in the current version in the git repository. In the case of identical source and target anchor the decision if (connection.getStart().equals(oldAnchor)) { might lead to the wrong conclusion since it is true even if the end point is to be changed. The method org.eclipse.graphiti.features.impl.DefaultReconnectionFeature.reconnect(IReconnectionContext) has to be changed according to attached snippet.
Reproducable in tutorial when reconnection is enabled
Thanks for pointing out and providing the fix! I took over your patch into our Head revision for Graphiti 0.9.0 (Juno M7) and added a test for this. Checked-in and pushed to Eclipse: commit 454dc526a7eaf68489729ae8e90e387e6e4b25a4 Author: mwenz <michael.wenz@sap.com> 2012-04-12 12:16:26 Committer: mwenz <michael.wenz@sap.com> 2012-04-12 12:16:26 Parent: 4a76009ff9dfbb4b33a4526e81f0078841c49356 (Bug 373298 - Fixed image resource leak in SVG export and cleaned up around unused image creation without dispose) Branches: origin/master, master
Part of Graphiti 0.9.0 (Eclipse Juno)