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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: tms13 [Submitted to the original trac issue database at 9.19am, Friday, 21st May 2010]
Create a polygon. Remove or detach a non-end node; the polygon is still closed. Remove or detach one of the terminal nodes, and the polygon now becomes a polyline terminated at the previously penultimate nodes.
If we're treating polygons cleverly when splitting, then we should be consistent when removing nodes from them.
The text was updated successfully, but these errors were encountered:
Author: tms13 [Added to the original trac issue at 10.27am, Sunday, 23rd May 2010]
That's what I think, given how we're careful to hide the mechanics of where the start/end is.
I think that the Right Thing is to detect this case and join the loose ends when the start/end node is removed from the way.
I'm willing to look into it myself now (I submitted the ticket when I was busy with other stuff, but I have the time and knowledge now). Stop me if you're already on it!
Reporter: tms13
[Submitted to the original trac issue database at 9.19am, Friday, 21st May 2010]
Create a polygon. Remove or detach a non-end node; the polygon is still closed. Remove or detach one of the terminal nodes, and the polygon now becomes a polyline terminated at the previously penultimate nodes.
If we're treating polygons cleverly when splitting, then we should be consistent when removing nodes from them.
The text was updated successfully, but these errors were encountered: