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

Sorting of input layer Layers in Processing "multiple inputs" widgets #25225

Closed
qgib opened this issue Oct 25, 2017 · 8 comments
Closed

Sorting of input layer Layers in Processing "multiple inputs" widgets #25225

qgib opened this issue Oct 25, 2017 · 8 comments
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 Oct 25, 2017

Author Name: Hans Fuchs (Hans Fuchs)
Original Redmine Issue: 17327
Affected QGIS version: 2.18.13
Redmine category:processing/core
Assignee: Victor Olaya


In Processing Tool Box Modules such as Gdal>Misc>Merge, Gdal>Misc>Build Virtual Raster or OTB >Image Manipulation>Images Concatenation the order of loaded raster layers in the Layers Panel is not correctly transferred to the input images layers list (Mutiple selection) of the Processing Toolbox modules. The order of the layer is random and cannot be changed which makes these modules useless.

OSGeo4W QGIS 2.18.13


Related issue(s): #25026 (relates), #25219 (duplicates)
Redmine related issue(s): 17127, 17321


@qgib
Copy link
Contributor Author

qgib commented Oct 25, 2017

Author Name: Giovanni Manghi (@gioman)


This is pretty much duplicate of #25026 but this is more general.

Is indeed a real issue: in the multiple inputs widgets there is the need to allow sorting of layers and the sorted list then transferred as it is in the command being executed.


  • category_id was changed from Processing/GUI to Processing/Core
  • subject was changed from Sorting of Raster Layers in Processing Toolbox Modules to Sorting of input layer Layers in Processing "multiple inputs" widgets

@qgib
Copy link
Contributor Author

qgib commented Oct 25, 2017

Author Name: Nyall Dawson (@nyalldawson)


This should be fixed in master - can you confirm?


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Oct 26, 2017

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


@qgib
Copy link
Contributor Author

qgib commented Nov 10, 2017

Author Name: Alexander Bruy (@alexbruy)


@qgib
Copy link
Contributor Author

qgib commented Nov 13, 2017

Author Name: Giovanni Manghi (@gioman)


Nyall Dawson wrote:

This should be fixed in master - can you confirm?

I just checked: is not completely fixed. In the multiple input widget you can as a fact d&d the layers to reorder them but:

  • having also arrows would be more intuitive for the users

  • d&d only kind of works: if in the list you d&d a layer over the name of another then one of the two is removed from the list

@qgib
Copy link
Contributor Author

qgib commented Jan 22, 2018

Author Name: Alister Hood (@AlisterH)


Should we change the status of this to "open", or open a new ticket (or close - I haven't checked if Giovanni's last point is still a problem)?

@qgib
Copy link
Contributor Author

qgib commented Jan 22, 2018

Author Name: Alister Hood (@AlisterH)


Hi guys, if you are using outputs from several uses of another algorithm (perhaps a smoothing algorithm or gdalwarp), and you drag them around to change the order, is there any way of knowing which one is which?
See #25824

@qgib
Copy link
Contributor Author

qgib commented Aug 23, 2018

Author Name: Giovanni Manghi (@gioman)


  • having also arrows would be more intuitive for the users

  • d&d only kind of works: if in the list you d&d a layer over the name of another then one of the two is removed from the list

I guess the arrows thing should be a feature request, the second issue seems fixed.


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

@qgib qgib closed this as completed Aug 23, 2018
@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 25, 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