Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify tool act weird when "search radius for identifying features" is set to 0% #12324

Closed
qgib opened this issue Dec 11, 2009 · 9 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Map and Legend Related to map or legend rendering
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Dec 11, 2009

Author Name: dr - (dr -)
Original Redmine Issue: 2264

Redmine category:map_canvas
Assignee: nobody -


If click alongside of the boundary of two polygons, both polygons is selected.

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: Giovanni Manghi (@gioman)


you can configure the sensitivity of this tools in the qgis options


  • status_id was changed from Open to Closed
  • resolution was changed from to invalid

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: dr - (dr -)


Replying to [comment:1 lutra]:

you can configure the sensitivity of this tools in the qgis options
I've configured 'search radius for identifying'.
In fact, 0% work the same as 100%. Is it bug?

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: Giovanni Manghi (@gioman)


In many software when you set "0" for some kind of configuration it means "No limit", so I guess this make sense.

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: dr - (dr -)


Replying to [comment:3 lutra]:

In many software when you set "0" for some kind of configuration it means "No limit", so I guess this make sense.
Thanks. But I can't find where I can configure select sensitivity.

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: Giovanni Manghi (@gioman)


Replying to [comment:4 dr]:

But I can't find where I can configure select sensitivity.

I guess you are right, seems to miss. If is the case, what is the suggestion, use the same sensitivity of the identify tool?

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: dr - (dr -)


I think use the same sensitivity for selection is a good idea.

I find strange thing.

  1. Set 0% identify radius;

  2. Select some feature and then press deselect features button;

  3. Try to identify some feature.

Identifiable feature is feature which was selected at 1 step.

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: Giovanni Manghi (@gioman)


confirmed

new description:

  1. Set 0% identify radius;

  2. Select some features and then press deselect features button;

  3. Try to identify some features.

Identifiable features are features which were selected at step 2 and the identify tool seems not able to identify more features.


  • status_id was changed from Closed to Feedback
  • resolution was changed from invalid to

@qgib
Copy link
Contributor Author

qgib commented Dec 11, 2009

Author Name: Giovanni Manghi (@gioman)


you may want to file also a enhancement ticket for the "select features" tool sensitivity.

@qgib
Copy link
Contributor Author

qgib commented Dec 23, 2009

Author Name: Jürgen Fischer (@jef-n)


fixed in 2dc2034 (SVN r12604).


  • resolution was changed from to fixed
  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Map and Legend Related to map or legend rendering labels May 24, 2019
@qgib qgib added this to the Version 1.4.0 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Map and Legend Related to map or legend rendering
Projects
None yet
Development

No branches or pull requests

1 participant