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
doubleclick on map get's polygon stuck in "self intersection" state #631
Comments
finishOn: dblclick
and allowSelfIntersection
togetherallowSelfIntersection: false
, doubleclick on map get's polygon stuck in intersection state
allowSelfIntersection: false
, doubleclick on map get's polygon stuck in intersection state
I've updated the title, as it turns out that it doesn't have anything to do with the |
Thx for reporting! This is already fixed in the develop branche #621 |
That's awesome! Regarding your finding. Is that a bug, or a feature? I think it is actually a nice user experience if a double click doesn't add a vertex. Especially in the mode where double click finishes the feature. This would prevent accidental vertex insertions, where users don't want to add a vertex, but just want to finish the feature. |
We can discuss about this but I use it to create the last vertex and then finish it at the same time. When I want to finish the polygon without creating a vertex I click on the first marker. @codeofsumit how do you see that? |
Would it be possible to publish a patch or prerelease that contains this bug fix? |
I will release a patch version within the next few days 👌 |
@codeofsumit Any idea when this patch is going to go out as an npm package. |
Yeah sorry for not having released sooner. I'm on it! |
When using both
allowSelfIntersection: false
, andfinishOn: dblclick
to finish polygons, the double click gets the polygon stuck in anintersecting
state.To reproduce: jsfiddle
Click the
draw polygon
buttonCreate a polygon with 3 (or more) vertices
Finish by clicking the mouse button twice (
dblclick
).Polygon is now stuck in an
intersecting
state, so it can't be closed/finished.The text was updated successfully, but these errors were encountered: