of course, I see. I was under the impression that apart from honoring
the option by using the method you would not run into problems if the
api changes.
Bernhard
Am 19.01.2017 um 10:47 schrieb Victor Olaya:
hmm, not a bad idea, but it is actually very easy to do that using
standard QGIS method
hmm, not a bad idea, but it is actually very easy to do that using
standard QGIS methods (you can see how simple the fix i made is). The
advantage of vector.features is that it honors the option setting,
without the developer having to take care of that.
Cheers
2017-01-19 10:43 GMT+01:00 Bernha
Hi Victor,
what do you think about enhancing processing's vector.features with an
additional optional flag that returns the selection no matter if the
option is set or not?
Bernhard
Am 19.01.2017 um 10:35 schrieb Victor Olaya:
Good catch
I fixed it and now it uses the selected features, re
Good catch
I fixed it and now it uses the selected features, regardless of the
config parameter. The change is in 2.18 and master branches
Thanks!
2017-01-18 10:44 GMT+01:00 Bernhard Ströbl :
> Hi all,
> processing sports the "Save selected features" algorithm. However if in
> processing's optio
Hi all,
processing sports the "Save selected features" algorithm. However if in
processing's options you untick "Use only selected features" the
algorithm outputs _all_ features of the input layer. Although I know
that processing works only on selections when the option is ticked IMHO
the curr
