There is no command to run and algorithm iteratively from the command line.
You can iterate creating yourself a loop and separating the features of the
input layer in the loop.
This method from the AlgorithmExecutor class might help you:
https://github.com/qgis/QGIS/blob/master/python/plugins/pro
https://groups.google.com/forum/#!topic/qextserialport/I5L6Omlw_z0
Just as an FYI, it appears that qextserialport isn't planning on supporting
Qt 5.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgi
On Tue, Jun 16, 2015 at 2:01 PM, Radim Blazek
wrote:
> Hi,
> I need to debug QGIS GRASS provider on Windows. I have successfully
> compiled GRASS 7 using MinGW [1] and QGIS using MSVC [2]. The problem
> is that MSVC does not support GCC debugging symbols and vice versa. Do
> you have any idea how
Gee, that was fast!
Thanks heaps.
Il 16 giugno 2015 19:26:10 GMT+00:00, Matthias Kuhn ha
scritto:
>Hi Paolo
>
>On 06/16/2015 07:51 PM, Paolo Cavallini wrote:
>> Hi all,
>> currently, the Unique value edit widget allows autocompletion (when
>> Editable option is active, but is case sensitive, so
Hi Paolo
On 06/16/2015 07:51 PM, Paolo Cavallini wrote:
> Hi all,
> currently, the Unique value edit widget allows autocompletion (when
> Editable option is active, but is case sensitive, so an user typing a
> will not be shown autocompletion for ABC.
> IMHO this is not intuitive, and is different
*No bites on the qgis-user list, cross-posting to developers to fish for
more help.*
Hi folks,
What is the python console syntax for the equivalent of pushing the
"iterate over layers" processing button when using runalg() ? e.g.
"p.runalg(... iterative=yes)".
>From "Additional functions for ha
Hi,
I need to debug QGIS GRASS provider on Windows. I have successfully
compiled GRASS 7 using MinGW [1] and QGIS using MSVC [2]. The problem
is that MSVC does not support GCC debugging symbols and vice versa. Do
you have any idea how to debug both QGIS and GRASS code at the same
time, preferably i
Hi all,
currently, the Unique value edit widget allows autocompletion (when
Editable option is active, but is case sensitive, so an user typing a
will not be shown autocompletion for ABC.
IMHO this is not intuitive, and is different from what users expect.
Should I open a ticket, or there are good
Hello,
Here an interesting commentary by a software engineer friend of mine who
seems a little more knowledgeable about open source licenses than the
author of the "Open Source Mania" article on LiDAR News:
http://odoepner.wordpress.com/2015/06/16/lidar-news-publishes-uninformed-gpl-rant/
The co
On Tue, Jun 16, 2015 at 02:27:10PM +0200, Matthias Kuhn wrote:
> In an ideal world, all internal code would be ported to the new API and
> some tests guarantee that the legacy API keeps working as expected.
> Sometimes it may also be ok to leave internal code use the deprecated
> API. It just has
On 06/16/2015 02:03 PM, Sandro Santilli wrote:
> On Tue, Jun 16, 2015 at 01:54:34PM +0200, Matthias Kuhn wrote:
>
>> The plan is to let travis test for warnings and if there are warnings
>> mark the build red. With this in place, an author of a commit will be
>> required to spend some thoughts on
On Tue, Jun 16, 2015 at 01:54:34PM +0200, Matthias Kuhn wrote:
> The plan is to let travis test for warnings and if there are warnings
> mark the build red. With this in place, an author of a commit will be
> required to spend some thoughts on a warning and take care of it before
> merging into ma
In the quest for an always closer-to-perfection state of code, some
goblins tried to get the warning count (on gcc and clang) yesterday as
close to zero as possible. This was done in order to allow you (as a
developer) to see if your code changes cause warnings without scrolling
through heaps of me
Hi,
i'm trying to help with bug fixing, testing QGIS after a bug ticket
(opened by me) is closed;
so i'm using qgis-dev (osgeo4w 32 bit) that should receive the changes,
i wonder
however when i should test the fix after i receive the "closed" status
by bug tracker,
AFAIK qgis-dev are nightly b
Ah: brushStyle(). Got it. Thanks.
Tom
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/API-fill-style-tp5211196p5211203.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
I need to get the "Fill style" of a simple fill symbol layer, but cannot find
that in the API docs. Does it exist? I need it to fix a reported bug in
qgis2web:
https://github.com/tomchadwin/qgis2web/issues/10
Specifically, I need to determine if a simple fill symbol layer has fill
style "No Brush
On 16-06-15 08:58, Arnaud Morvan wrote:
> I've see that processing algs documentation have been refactorized, for
> now there is one .rst file for each group instead of one file for each
> algorithm in the past.
> This should have been made to reduce the number of files.
Hi Arnaud,
Yes, we went '
17 matches
Mail list logo
