Opened 13 years ago
Closed 10 years ago
#5922 closed defect (fixed)
[patch] value of createcircle.nodecount not always applied
Reported by: | malenki | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | 14.03 |
Component: | Core | Version: | |
Keywords: | create circle | Cc: |
Description (last modified by )
Lets say, we set a value of 24.
Now draw a line with two nodes, press shift-o. The created circle contains 24 Nodes
Now draw a triangle and press shift-o. The created circle contains 24+3 nodes.
The nodes of which the triangle existed remain unaltered and thus cause also a not regular arrangement of nodes.
Attachments (1)
Change History (7)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
There is a new method? What is the old one?
The way I described to create a circle based on a triangle finishes with the way selected.
I see your points in "not deleting" the nodes from the previous triangle, but I did not ask to delete them.
comment:3 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Keywords: | create circle added |
comment:4 Changed 10 years ago by
Summary: | value of createcircle.nodecount not always applied → [patch] value of createcircle.nodecount not always applied |
---|
I a put a patch.
Insert nodes regularly between existing nodes to achieve createcircle.nodecount
total number of nodes.
I prefer the new method.
You get an equal distribution of the 'created' nodes and the given nodes can easily be deleted, because they are still marked.
On the other hand you may wish to use the 'construction' nodes (e.g. as entry points at a roundabout), so I won't prefer an automatic delete.