-
Notifications
You must be signed in to change notification settings - Fork 856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat]: Manhattan router should support ports inside the element's body. #2763
Comments
@kumilingus ping 👀 |
|
Ahh, I see. The step size is used to "jump" from the "real port" to the "fake port" (the |
Let me reopen this issue with a goal of supporting it at some point. |
Current versus expected behaviour
Note
This is a follow up from #2738 (reply in thread)
Hi @kumilingus !
I've been playing around with the code you gave me in the manhattan-router discussion the other day and I saw something that I thought is worth mentioning. Certain situations lead to the manhattan router creating extra vertices:
I'm aware that this might be (¿?) caused by the
step
option and because of the way collisions are detected (¿?), which is fine, but if I set thestep
value to1
(actually any value below7
), manhattan just stops avoiding any obstacles at all.I tried debugging the code and re-reading all the docs, and I believe there is a correlation between
step
andgridSize
, but setting the later to the same value doesn't fix the problem.Why isn't manhattan avoiding obstacles when
step < 7
?Steps to reproduce
step
to any value below7
Version
4.0.4
What browsers are you seeing the problem on?
Chrome, Safari
What operating system are you seeing the problem on?
Mac
The text was updated successfully, but these errors were encountered: