small local changes in node position have unexpected global effects #435
Replies: 5 comments
-
|
Hi, Please let me know if this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Sure - I’ll give it a try tonight
Sent from my iPhone
On Jan 12, 2026, at 1:18 AM, Ralph Soika ***@***.***> wrote:
Hi,
I guess you are working in a diagram without pools? I observed this behavior also but was not able to reproduce it directly.
I think this is a regression in our new 'optimized' routing algorithm.
Can you try the last release 1.1.24 - you can install this extension as a vsix file
https://github.com/imixs/open-bpmn-vscode-integration/releases/tag/open-bpmn-vscode-integration-1.1.24
Please let me know if this helps.
—
Reply to this email directly, view it on GitHub<#435 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJZB6PLTTGD5HKTN4MW6VR34GNRHLAVCNFSM6AAAAACRLTWRXSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBXGM2TCMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I was able to isolate the bug with a simplified model file. So now we can better analyze what is going wrong here.... |
Beta Was this translation helpful? Give feedback.
-
|
Hi @chrisesposito4 |
Beta Was this translation helpful? Give feedback.
-
|
Hi Ralph, Thanks for the quick fix. It appears to work corerctly now.
Chris
…________________________________
From: Ralph Soika ***@***.***>
Sent: Tuesday, January 13, 2026 12:39 PM
To: imixs/open-bpmn ***@***.***>
Cc: Chris Esposiro ***@***.***>; Mention ***@***.***>
Subject: Re: [imixs/open-bpmn] small local changes in node position have unexpected global effects (Discussion #435)
Hi @chrisesposito4<https://github.com/chrisesposito4>
we just published the new version 1.1.27 of the Open-BPMN Extension for VS-Code. The new version should be installed automatically.
With this version your problem hopefully are now solved. I look forward to your feedback :-)
—
Reply to this email directly, view it on GitHub<#435 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJZB6POIM3AYBB24EVK4ZT34GVJZPAVCNFSM6AAAAACRLTWRXSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBYHE2DENY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm seeing a problem in network redraws that I can reproduce. I have a reasonably sized network, maybe 50 nodes and 100+ edges. If I have a task node that has 1 input and 1 output (so not directly connected to the rest of the network) and I move it by a very small amount (a few pixels in any direction) then the edges in distant parts of the network are rerouted in a way that makes the network layout vastly more cluttered - edges get longer, less direct than they were, and with more bends. The node stay where they are. Is there a setting I can turn off for this? It seems to me that moving a single node ought to only affect the edges it is connected to.
Beta Was this translation helpful? Give feedback.
All reactions