Opened 14 years ago
Closed 13 years ago
#2973 closed bug (fixed)
Selection tool is not selecting a complex object
Reported by: | gislab | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.6.0 |
Component: | MapCanvas | Version: | Trunk |
Keywords: | Cc: | dr, alexbruy, jef | |
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
Try selecting a big polygon in a attached shapefile with the first selection tool. Big polygon cannot be selected, while smaller ones are selected alright.
Rings and self-intersection error are present in the big polygon, not sure if this is related though.
Attachments (2)
Change History (11)
by , 14 years ago
Attachment: | e008n07f.zip added |
---|
comment:1 by , 14 years ago
Cc: | added |
---|
comment:2 by , 14 years ago
Type: | bug → patch |
---|
by , 14 years ago
Attachment: | single_select.patch added |
---|
comment:3 by , 14 years ago
can somebody review and apply? current behavior makes selection tool unusable in many circumstances
comment:4 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
applied in r14259. Thanks again Jeremy.
comment:5 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Type: | patch → bug |
Version: | → Trunk |
Select features by rectangle, by polygon, by radius and by freehand doesn't work on this polygon.
comment:6 by , 14 years ago
I can get it to work for all of the select tools on this dataset.
I suspect the problem dr is having is the selection tools now use contains rather than intersects by default. Maybe the best solution is to make intersects the default method for all selection tools. Then provide an option to change it to contains if the user prefers.
I have made a patch patch in #2938 that hopefully addresses this issue.
comment:7 by , 14 years ago
Cc: | added |
---|---|
Must Fix for Release: | No → Yes |
Platform: | Windows → All |
comment:8 by , 14 years ago
this would be really nice if it can work in both modes! I agree that default 'intersect' makes a lot of sense. Thanks for working on this.
comment:9 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Seems to be fixed. 'Intersect' selection mode is default now.
Yip there is a bug in the single select tool. The tool made the assumption that feature ids are always >0, when in fact a feature id can be 0 and in the case of editing can be negative integer values. The attached patch fixes the issue.