Opened 2 years ago
Last modified 2 years ago
#5922 new defect
value of createcircle.nodecount not always applied
| Reported by: | malenki | Owned by: | team |
|---|---|---|---|
| Priority: | minor | Component: | Core |
| Version: | Keywords: | ||
| Cc: |
Description
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 (0)
Change History (2)
comment:1 Changed 2 years ago by GeorgFausB
comment:2 Changed 2 years ago by malenki
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.



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.