You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current isPointInsidePath() implementation launches an horizontal ray and counts how many times it intersects the path. However it relies on interHelper() which has trouble finding intersections lying exactly at path vertex coordinates. This causes the issue reported in #563 that #594 attempted to fix.
Obviously interHelper() needs fixing, but because that is a complex task I suggest instead to add some jitter to the ray destination in isPointInsidePath(), which is trivial and harmless. Instead of:
The current
isPointInsidePath()
implementation launches an horizontal ray and counts how many times it intersects the path. However it relies oninterHelper()
which has trouble finding intersections lying exactly at path vertex coordinates. This causes the issue reported in #563 that #594 attempted to fix.Here is an example of an obvious failure:
Obviously
interHelper()
needs fixing, but because that is a complex task I suggest instead to add some jitter to the ray destination inisPointInsidePath()
, which is trivial and harmless. Instead of:Use:
The text was updated successfully, but these errors were encountered: