Re: [Qgis-developer] Replacing Q_FOREACH in Qgis code

[Larry Shaffer]

Hi David,

Thanks for bringing this up. After reading the referenced KDAB article (and
especially the not-so-happy comments about this deprecation), I looked at
the code base.

Instances of Q_FOREACH in QGIS 2.99 (master): 2023

Why can't Qt just leave the macro in and recommend using a better C++11
construct for devs wishing better performance? (rhetorical question)

I guess the macro can be added to a QGIS header file while devs spend their
time endlessly figuring out how to do a port "for each" Q_FOREACH.

I, for one, find this a bit annoying on Qt's part, but still understand the
reasoning for it.

Larry Shaffer
Dakota Cartography
Black Hills, South Dakota

On Thu, Jan 19, 2017 at 3:28 AM, David Marteau  wrote:

> Hi,
>
> I would like to know if there is plans for replacing Q_FOREACH (use
> discouraged from QT 5.7) with C++11 range based loop in QGIS code and if it
> is appropriate to start the move in new PR ?
>
> Some références:
> http://doc.qt.io/qt-5/qtglobal.html#Q_FOREACH
> http://en.cppreference.com/w/cpp/language/range-for
> https://www.kdab.com/goodbye-q_foreach/
>
> Thx
> David
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] What SAGA version is recommended?

[Andreas Neumann]

ok - I finally got SAGA 2.3.1 working after patching the io_gdal command 
in file SagaAlgorithm214.py to use the "RESAMPLING" parameter instead of 
the "INTERPOL" one - just as described by gcarillo in 
http://hub.qgis.org/issues/14735


Thanks for the help!

Andreas


On 19.01.2017 09:47, matteo wrote:

Hi all,


this is a long standing issue. IMHO the reasonable choice is to support
the SAGA LTR, and convince packagers for various OSs this is the one to
package.
I'm interested on this, available for help.

me too.. available for testing and/or general helping.

Sometimes running SAGA algorithms after an upgrade means having faith ;)

Cheers

Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Interrupt WFS request not working?

[Even Rouault]

On jeudi 19 janvier 2017 18:34:28 CET Paolo Cavallini wrote:
> Hi all,
> I tried today to interrupt a slow WFS request, with the button on the
> dialog, but I got no effect: is this a known limitation, a bug, or am I
> missing something?

It is supposed to work. Do you reproduce that with a specific WFS endpoint 
(in which case which one?) or with all endpoints ?

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [1163] Plugin Load Times approval notification.

[noreply]

Plugin Plugin Load Times approval by pcav.
The plugin version "[1163] Plugin Load Times 0.5 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/PluginLoadTimes/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [1163] Plugin Load Times approval notification.

[noreply]

Plugin Plugin Load Times approval by pcav.
The plugin version "[1163] Plugin Load Times 0.5.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/PluginLoadTimes/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [1163] Plugin Load Times approval notification.

[noreply]

Plugin Plugin Load Times approval by pcav.
The plugin version "[1163] Plugin Load Times 0.5.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/PluginLoadTimes/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Interrupt WFS request not working?

[Paolo Cavallini]

Hi all,
I tried today to interrupt a slow WFS request, with the button on the
dialog, but I got no effect: is this a known limitation, a bug, or am I
missing something?
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [740] qgis2web approval notification.

[noreply]

Plugin qgis2web approval by pcav.
The plugin version "[740] qgis2web 2.2.0" is now approved
Link: http://plugins.qgis.org/plugins/qgis2web/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] [Server] 2.14: Selection in GetPrint doesn't work

[René-Luc Dhont]

Hi dev,

I'm facing a strange issue in GetPrint. The SELECTION is not apply to 
the MapComposer.
The code is quite old: 
https://github.com/qgis/QGIS/blame/release-2_14/src/server/qgswmsserver.cpp#L1273

And there is no test to verify it.

Do someone know how selection is apply to MapComposer ?
Do someone know how to apply a selection to MapComposer ?

Thanks
René-Luc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Processing ctest for QGIS timeout

[matteo]

Hi guys,

this issue is still there, I'm not able to run ProcessingQgis tests

I also tried to comment the last tests uploaded (that some days ago run
without problem) but it does not solve the problem.

Any hints?

Thanks again

Cheers

Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Python bindings for "QgsMapToolCapture"

[Matthias Kuhn]

Hi Bo,

2.18.2 here:

from qgis.gui import QgsMapToolCapture
tool = QgsMapToolCapture()

Hint: You probably want to subclass QgsMapToolCapture

Matthias
On 01/19/2017 03:33 PM, Bo Victor Thomsen wrote:
> To the QGIS developers (and not a newbie QGIS plugin developer like me) -
> 
> Is there a QGIS python binding for class "QgsMapToolCapture". Or do I
> have to recreate the various point, line and polygon capture tools ?
> 
> My goal is to have 3 tools (point, line and polygon capture) available
> though a QGIS plugin and show the capture -  result in the canvas using 
> QgsRubberBand. I can't find any documentations for the python bindings
> for QgsMapToolCapture and I guess that they doesn't exist.
> 
> I refuse to believe I'm the only one having this problem - So:
> 
>   * Does the python bindings exist or not ?
>   * If the first answer are "not": Is there some QGIS / qt / python
> based replacement for "QgsMapToolCapture" ??
> 
> Regards
> 
> Bo Victor Thomsen
> 
> 
> 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Python bindings for "QgsMapToolCapture"

[Bo Victor Thomsen]

To the QGIS developers (and not a newbie QGIS plugin developer like me) -

Is there a QGIS python binding for class "QgsMapToolCapture". Or do I 
have to recreate the various point, line and polygon capture tools ?


My goal is to have 3 tools (point, line and polygon capture) available 
though a QGIS plugin and show the capture -  result in the canvas using  
QgsRubberBand. I can't find any documentations for the python bindings 
for QgsMapToolCapture and I guess that they doesn't exist.


I refuse to believe I'm the only one having this problem - So:

 * Does the python bindings exist or not ?
 * If the first answer are "not": Is there some QGIS / qt / python
   based replacement for "QgsMapToolCapture" ??

Regards

Bo Victor Thomsen



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Minor UI issue on Geoprocessing tools → Convex hull

[Jorge Gustavo Rocha]

Hi devs,

This discussion addresses a minor UI issue in the Convex hull dialog
(under Vector → Geoprocessing tools).

The Convex hull dialog [1] has two independent options, which are:
Field, to create convex hulls by classes
Method: to create a single convex hull or convex hulls by classes

Current issues:

1) If the user selects a field in the first combobox, to create convex
hulls by classes, but leaves the second combobox with the default option
"Create single minimum convex hull", the convex hull is not done by
classes, but for all geometries. Probably it is not what the user wants.

2) If the user does not select a field in the first combobox, but
selects the method "Create convex hulls based on field", the operation
tries to do something, but fails with: "float division by zero".
Obviously this does not make sense, but it is allowed by the interface.

My proposal is to enhance this dialog, to provide a better user
experience with these two related options.

I see two possible alternatives:

a)
* The order of these two fields changes.
* First the user has to select the method.
* The field combobox only gets enabled if the method is "Create convex
hulls based on field" is selected in the Method combobox.
* When the user changes the method back to "Create single minimum convex
hull", the Field combobox is disabled.

b)
* We drop the Method combobox at all,
* We use just one dropbox to select a field
* If no field is selected, the method is "Create single minimum convex
hull".
* If a field is selected, the method is "Create convex hulls based on
field".

I can make a PR to improve this, but I would like to discuss what is the
best approach here.

Regards,

[1] http://webgis.di.uminho.pt/~jgr/convex%20hull%20dialog.png

J. Gustavo
-- 
Jorge Gustavo Rocha
Departamento de Informática
Universidade do Minho
4710-057 Braga
Tel: +351 253604480
Fax: +351 253604471
Móvel: +351 910333888
skype: nabocudnosor
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS Server in Python?

[Alessandro Pasotti]

On Thu, Jan 19, 2017 at 11:03 AM, Sören Gebbert <
soerengebb...@googlemail.com> wrote:

> Dear developers,
> i have a naive question.
>
> Would it be possible and meaningful to implement the QGIS Server in Python?
>
> There are several nice Python Web-frameworks (Django, Flask) which would
> make it easy to expose the rendering, data management and processing
> functionality of QGIS as WMS, WFS or REST service.
>
> Do you think this may be a good idea to implement?
>

You can do that right now:
https://github.com/qgis/QGIS/blob/master/tests/src/python/qgis_wrapped_server.py

But after the refactoring that we are doing it will be even simpler.

There is also a WPS plugin for QGIS server.

-- 
Alessandro Pasotti
w3:   www.itopen.it
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Z or M styling in QGIS

[Régis Haubourg]

Hi all, 

playing with my experimental Z styles I noticed strange rendering issues
with vertices not being rendered at the right place. 
See short screen cast here  https://youtu.be/NdoyysCzEUs


I'm filing that in 
Does that look like a bug underneath in QGIS or an error in my expressions ?

Cheers
Régis 



-
--
Régis Haubourg
GIS administrator and project manager
Administrateur de données géographiques et chef de projet SIG
Agence de l'eau Adour-Garonne 

--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Z-or-M-styling-in-QGIS-tp5301770p5304004.html
Sent from the QGIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS Server in Python?

[Jürgen E . Fischer]

Hi Sören,

On Thu, 19. Jan 2017 at 11:03:29 +0100, Sören Gebbert wrote:
> Do you think this may be a good idea to implement?

Something in the direction of https://github.com/wonder-sk/qgis-tile-server


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode 



pgp9G5zfOUwFu.pgp
Description: PGP signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS Server in Python?

[David Marteau]

Hi,

The server is actually under heavy refactoring: the new version - planned with 
Qgis 3 - enables you to embed the server in any  framework (python or C++) by 
using abstract request/response objects that links all I/O between server and 
your embedding frameworks. Examples will follow soon.

David.


> Le 19 janv. 2017 à 11:03, Sören Gebbert  a 
> écrit :
> 
> Dear developers,
> i have a naive question.
> 
> Would it be possible and meaningful to implement the QGIS Server in Python?
> 
> There are several nice Python Web-frameworks (Django, Flask) which would make 
> it easy to expose the rendering, data management and processing functionality 
> of QGIS as WMS, WFS or REST service.
> 
> Do you think this may be a good idea to implement?
> 
> Thanks and best regards
> Soeren 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] QGIS Server in Python?

[Sören Gebbert]

Dear developers,
i have a naive question.

Would it be possible and meaningful to implement the QGIS Server in Python?

There are several nice Python Web-frameworks (Django, Flask) which would
make it easy to expose the rendering, data management and processing
functionality of QGIS as WMS, WFS or REST service.

Do you think this may be a good idea to implement?

Thanks and best regards
Soeren
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Processing] how to handle selections

[Bernhard Ströbl]

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 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 Bernhard Ströbl <bernhard.stro...@jena.de>:

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, 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 <bernhard.stro...@jena.de>:


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 current
behaviour is not intuitive: if an algorithm in its name (and help) claims
to
do something with the selected features it should do that _all the time_.
Opinions?

Background: I opened a PR [1] yesterday for an algorithm that works on
selected features all the time (won't make sense otherwise) and would
like
processing to be consistent in that respect.

regards

Bernhard

[1] https://github.com/qgis/QGIS/pull/4011


__ Information from ESET Mail Security, version of virus
signature
database 14787 (20170118) __

The message was checked by ESET Mail Security.
http://www.eset.com


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer




__ Information from ESET Mail Security, version of virus signature
database 14793 (20170119) __

The message was checked by ESET Mail Security.
http://www.eset.com






__ Information from ESET Mail Security, version of virus signature
database 14793 (20170119) __


The message was checked by ESET Mail Security.
http://www.eset.com





__ Information from ESET Mail Security, version of virus signature 
database 14793 (20170119) __

The message was checked by ESET Mail Security.
http://www.eset.com






__ Information from ESET Mail Security, version of virus signature 
database 14793 (20170119) __

The message was checked by ESET Mail Security.
http://www.eset.com


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Processing] how to handle selections

[Victor Olaya]

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 Bernhard Ströbl <bernhard.stro...@jena.de>:
> 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, 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 <bernhard.stro...@jena.de>:
>>>
>>> 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 current
>>> behaviour is not intuitive: if an algorithm in its name (and help) claims
>>> to
>>> do something with the selected features it should do that _all the time_.
>>> Opinions?
>>>
>>> Background: I opened a PR [1] yesterday for an algorithm that works on
>>> selected features all the time (won't make sense otherwise) and would
>>> like
>>> processing to be consistent in that respect.
>>>
>>> regards
>>>
>>> Bernhard
>>>
>>> [1] https://github.com/qgis/QGIS/pull/4011
>>>
>>>
>>> __ Information from ESET Mail Security, version of virus
>>> signature
>>> database 14787 (20170118) __
>>>
>>> The message was checked by ESET Mail Security.
>>> http://www.eset.com
>>>
>>>
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>>
>> __ Information from ESET Mail Security, version of virus signature
>> database 14793 (20170119) __
>>
>> The message was checked by ESET Mail Security.
>> http://www.eset.com
>>
>>
>
>
>
> __ Information from ESET Mail Security, version of virus signature
> database 14793 (20170119) __
>
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Processing] how to handle selections

[Bernhard Ströbl]

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, 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 <bernhard.stro...@jena.de>:

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 current
behaviour is not intuitive: if an algorithm in its name (and help) claims to
do something with the selected features it should do that _all the time_.
Opinions?

Background: I opened a PR [1] yesterday for an algorithm that works on
selected features all the time (won't make sense otherwise) and would like
processing to be consistent in that respect.

regards

Bernhard

[1] https://github.com/qgis/QGIS/pull/4011


__ Information from ESET Mail Security, version of virus signature
database 14787 (20170118) __

The message was checked by ESET Mail Security.
http://www.eset.com


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



__ Information from ESET Mail Security, version of virus signature 
database 14793 (20170119) __

The message was checked by ESET Mail Security.
http://www.eset.com






__ Information from ESET Mail Security, version of virus signature 
database 14793 (20170119) __

The message was checked by ESET Mail Security.
http://www.eset.com


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Processing] how to handle selections

[Victor Olaya]

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 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 current
> behaviour is not intuitive: if an algorithm in its name (and help) claims to
> do something with the selected features it should do that _all the time_.
> Opinions?
>
> Background: I opened a PR [1] yesterday for an algorithm that works on
> selected features all the time (won't make sense otherwise) and would like
> processing to be consistent in that respect.
>
> regards
>
> Bernhard
>
> [1] https://github.com/qgis/QGIS/pull/4011
>
>
> __ Information from ESET Mail Security, version of virus signature
> database 14787 (20170118) __
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Replacing Q_FOREACH in Qgis code

[David Marteau]

Hi,

I would like to know if there is plans for replacing Q_FOREACH (use discouraged 
from QT 5.7) with C++11 range based loop in QGIS code and if it is appropriate 
to start the move in new PR ?

Some références:
http://doc.qt.io/qt-5/qtglobal.html#Q_FOREACH
http://en.cppreference.com/w/cpp/language/range-for
https://www.kdab.com/goodbye-q_foreach/

Thx
David
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] What SAGA version is recommended?

[matteo]

Hi all,

> this is a long standing issue. IMHO the reasonable choice is to support
> the SAGA LTR, and convince packagers for various OSs this is the one to
> package.
> I'm interested on this, available for help.

me too.. available for testing and/or general helping.

Sometimes running SAGA algorithms after an upgrade means having faith ;)

Cheers

Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer