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

fTools:Select by location is confusing, especially with an empty selection #15403

Closed
qgib opened this issue Jul 11, 2012 · 8 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Jul 11, 2012

Author Name: Leyan Ouyang (Leyan Ouyang)
Original Redmine Issue: 6018
Affected QGIS version: master
Redmine category:processing/qgis


I used "Select by location" in the fTools plugin, with the options to use selected features only. The progress bar started the movement left and right used for an unknown amount of remaining time, so I waited, surprised that my small data set was so hard to select.

Actually, the selection was empty and no calculation was happening, but it took me the longest time to realize it. The problem is twofold:

  • nothing prevents using an empty selection (even if it cannot be useful), but self.progressBar.setMaximum(len(features)) on line 114 of doSelectByLocation.py does not have the expected result when features is an empty list as it makes an endlessly moving progress bar
  • More globally, the plugin doesn't indicate anything when the computation is finished. I would have expected either closing the window or at least showing a message indicating the number of selected features. Something like: "%d features have been selected, the existing selection had %d features, the new selection has %d features" % (nbSelected, nbPrevious, nbEndResult) ))@ at the end of the compute() function

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was configured as Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Jul 13, 2013

Author Name: Giovanni Manghi (@gioman)


The first issue does not seems to happen (anymore).

About the second suggestion, the number of selected features is shown in the left bottom corner of the main qgis window.


  • status_id was changed from Open to Closed
  • fixed_version_id was changed from Version 2.0.0 to Future Release - Nice to have
  • resolution was changed from to worksforme

@qgib
Copy link
Contributor Author

qgib commented Jul 13, 2013

Author Name: Leyan Ouyang (Leyan Ouyang)


The problem still exists in the latest Master build. Clear all selection, start "select by location" tool, check the "use selected feature only" (I agree it does not make sense, but one can check it by mistake like I did the first time). Then when starting the process no actual computation happens (well, there aren't any feature to consider) but the progress bar is continuously moving, which is very misleading.


  • status_id was changed from Closed to Reopened

@qgib
Copy link
Contributor Author

qgib commented Jul 13, 2013

Author Name: Giovanni Manghi (@gioman)


Leyan Ouyang wrote:

The problem still exists in the latest Master build. Clear all selection, start "select by location" tool, check the "use selected feature only" (I agree it does not make sense, but one can check it by mistake like I did the first time). Then when starting the process no actual computation happens (well, there aren't any feature to consider) but the progress bar is continuously moving, which is very misleading.

I tested another dataset and still works fine here. If there are no features selected and then the "use selected features only" is checked, then the tool works as it is expected (at least for me)... using all features to make the selection.


  • status_id was changed from Reopened to Feedback

@qgib
Copy link
Contributor Author

qgib commented Sep 13, 2013

Author Name: Leyan Ouyang (Leyan Ouyang)


Sorry, I forgot to provide feedback about this bug. Here is a screencast of what I mean.


  • 6232 was configured as qgis_select_by_location.mkv

@qgib
Copy link
Contributor Author

qgib commented Sep 14, 2013

Author Name: Giovanni Manghi (@gioman)


Ok, now I see it.


  • status_id was changed from Feedback to Open
  • priority_id was changed from Normal to Low
  • resolution was changed from worksforme to

@qgib
Copy link
Contributor Author

qgib commented Mar 25, 2016

Author Name: Alexander Bruy (@alexbruy)


Does not happen anymore with Processing. Please reopen if necessary


  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


The "ftools" category is being removed from the tracker, changing the category of this ticket to "Processing/QGIS" to not leave the category orphaned.

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 24, 2019
@qgib qgib added this to the Future Release - Nice to have 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! Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Development

No branches or pull requests

1 participant