Open alexandernst opened 1 month ago
@kumilingus ping 👀
30
pixels but only 20
pixels from the edge of the shape, the loop is gone (there is no need for it)manhattan
router does not work well with ports inside the element. If the step is to small to exit the shape (starting at the position of the port), then the fallback route is used.Ahh, I see. The step size is used to "jump" from the "real port" to the "fake port" (the pS
and pT
points in my code). If the step size doesn't cover the size of the "jump", it fallbacks. In my case, setting step to <7 will cause the fallback since the radius of the port itself is 5 and I have a margin of 2. That makes sense! It makes my brain hurt 🤔, but it makes sense.
Thank you!!
Let me reopen this issue with a goal of supporting it at some point.
Current versus expected behaviour
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