Opened 14 years ago
Last modified 13 years ago
#2301 new bug
problem when editing adjacent polygons and "enable toplogical editing" not active
Reported by: | lutra | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | Digitising | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
Take two adjacent polygons and check that in the project properties the "enable toplogical editing" option is not enabled.
With the node tool select one node of the sahred border and move it above the other polygon.
As a result the reshaped area stays under the other polygon instead of above. The new position of the node is marked but is like a point.
See screenshot.
Tested on trunk.
Attachments (1)
Change History (5)
by , 14 years ago
Attachment: | Screenshot-1.png added |
---|
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Replying to mhugent:
So I wonder if this should be classified as bug.
I believe that this "bug" takes origin from the following.
Take two adjacent polygons and leave "enable toplogical editing" disabled. Then with the node tool add nodes along a "common" segment. Obviously the new nodes are added only to the active polygon.
To show this new nodes as belonging only to one of the two polygons, the markers are rendered has half circles (I know that now are crosses, but it is the same), because I guess the other half is rendered under the adjacent polygon.
This is ok, but when it comes to reshape a polygon in a way that it has to overlap the adjacent one, then you see the described behavior. The problem is this way you can see the nodes but you cannot see the new shape.
I understand it might be a not very common situation but it can happen indeed.
comment:3 by , 14 years ago
Milestone: | Version 1.5.0 → Version 1.6.0 |
---|
comment:4 by , 13 years ago
Must Fix for Release: | Yes → No |
---|
Hm, the editing tool has no possibility to influence the order in which the features are drawn (it comes from the data source). So I wonder if this should be classified as bug.